Full technical documentation for the Travel Code API is published on a dedicated subdomain:
https://apidocs.travel-code.com/
What's inside
- Reference for every endpoint with parameters and possible responses.
- Data schemas (request/response, field types, required parameters).
- Authentication overview (OAuth tokens, scopes, refresh flow).
- Request samples (curl, JavaScript, Python).
- Error codes and response codes.
Who it's for
The documentation is intended for technical integrators and customer IT teams who connect their system (Concur, Egencia, SAP Concur, Sabre, Amadeus, Cytric, AmTrav, Deem, or in-house) to Travel Code directly via API.
If you're a travel manager and not doing the integration yourself, just forward https://apidocs.travel-code.com/ to your technical contact.
Frequently asked questions
Do I need an API key just to read the documentation? No, the documentation itself is publicly accessible — you can open and read it without credentials. API keys and OAuth tokens are required for the actual endpoint calls, not for browsing the docs.
How do I get API access for an integration? Contact us — we'll issue credentials (client_id / secret) and recommend the endpoints for your scenario. Standard authentication is OAuth 2.0.
Is there a sandbox environment? Yes. Sandbox terms and access are agreed during the discovery call before integration work starts.
Can I connect without using the API — via email forwarding or CSV? Yes, both are supported when API integration isn't available. See the Bring Your Own Data (BYOD) — how it works guide.
If you have questions
Write to our support chat or to support@travel-code.com. For technical API questions please mention which endpoints you're trying to use and what isn't working — that helps us reply faster.