Platform
One API
What is it
One API is the traveldistro integration model: a single authentication scheme, a single request envelope and a single error catalogue across every travel vertical. Integrate once, and each new vertical is a new endpoint, not a new project.
Capabilities
One request envelope
Every response returns the same data and meta shape, with a request id for tracing.
One error catalogue
The same machine-readable error codes across tickets, transfers, cars, eSIM and more.
Verticals as endpoints
Adding a vertical means calling a new path with credentials you already have.
GET /v1/account
Authorization: TD-HMAC-SHA256 KeyId=key_29xk, Signature=9f41…
X-TD-Timestamp: 1785603201
X-TD-Nonce: 5b1e-8c02
{
"data": { "name": "Acme Travel", "status": "active" },
"meta": { "request_id": "req_01JG7X…", "locale": "en" }
}Frequently asked questions
- Do I need separate keys per vertical?
- No. One API key and one signature scheme cover every vertical on your contract.
- What happens when new verticals launch?
- They appear as new endpoints under the same contract. Your authentication and wallet do not change.
Related pages
- Wallet & billingOne prepaid balance, multi-currency
- ReliabilityError catalogue, idempotency, uptime
- SecurityHMAC signing, key management, IP allowlist
Ready to integrate?
Tell us about your volume and verticals. We will get you sandbox keys.