Broad API Field Implementation - the more the better

Implement the maximum number of fields and endpoints instead of the minimum to reduce future development work and support multiple suppliers with different requirements.

Travel Curious Suppliers might use all the functionalities and fields available in our APIs or just part of them, it depends on their requirements and product needs. To avoid future issues and delays we recommend you to implement as much as possible when developing to our Reseller API, so instead of focusing on the pilot partner use case only, take a broader approach, anticipating that for a second or third Supplier connection you might need to have additional fields implemented to make sure you get the data needed.

Future-Proof Your Integration: By mapping additional API fields now, you’ll reduce future onboarding work when connecting with new suppliers.

Optimize for Multiple Connections: Implement fields not only for the pilot partner but in anticipation of broader supplier needs.

Example: Map all available fields in the initial integration phase, anticipating different data requirements for future suppliers.