August 1, 2026 · Alper Tekin
Introducing traveldistro: one API for every travel product
Why we built a B2B travel API marketplace, and what one key, one balance and one error catalogue mean for agencies.
Travel distribution has a wiring problem. An agency that wants to sell attraction tickets, tours, transfers, rental cars, eSIMs and hotels ends up signing six contracts, integrating six APIs, reconciling six invoices and learning six different ways to fail.
traveldistro replaces that pile with one contract. A single API key unlocks every vertical. A single prepaid balance settles every booking, in TRY, USD, EUR or GBP. A single error catalogue means your integration handles failure the same way everywhere.
What "one integration" actually means
Most platforms say it; here is what we ship:
- One request envelope. Every response returns the same
dataandmetashape, with a request id for tracing. - One authentication scheme. TD-HMAC-SHA256 request signing with timestamps and single-use nonces. No bearer tokens to leak.
- Idempotency everywhere it matters. Booking endpoints require an
Idempotency-Key, so a network retry can never double-book. - Errors as a contract. Stable machine-readable codes like
QUOTE_EXPIREDandINSUFFICIENT_BALANCE, never blank 500s.
Built by operators
The group behind traveldistro runs tour operations, hotel distribution and travel software across İstanbul, Edirne and Dubai, and publishes peer-reviewed research on travel distribution. The API is the productised version of how we already run inbound travel every day.
Where to start
Read the API reference, then talk to us about sandbox keys. Quote a product, redeem the quote as a booking, and you have seen the whole model.