Travel APIs
One REST surface for every travel product
A marketplace card per API, each stating what it covers, how it behaves under supplier latency, and what it deliberately does not do yet.
What travel APIs does TravelCore offer?
TravelCore publishes REST APIs for hotels, flights, transfers, activities, car rental and payments, sharing one authentication model, one error vocabulary and one idempotency rule. The hotel API is in design-partner preview; the others are specified and documented but not yet built. Every endpoint page states which of those two things is true.
Hotel API
Hotels
Multi-supplier accommodation search, booking and cancellation behind one contract.
- Coverage
- Coverage is the union of the suppliers you are contracted with. Large aggregators in this market publish counts in the range of 1M to 2.5M properties; the number you actually see depends on your own supplier agreements, the markets they cover, and the rate types you are entitled to. TravelCore does not own hotel inventory and does not resell a coverage figure it cannot verify for your account.
- Endpoints
- 6
- Auth
- OAuth 2.0
Flight API
Flights
Schedules, fares, availability and ticketing through one normalised interface.
- Coverage
- Planned via GDS and NDC aggregation. No coverage claim is made until the first carrier or aggregator contract is signed.
- Endpoints
- 5
- Auth
- OAuth 2.0
Transfers API
Transfers
Airport and point-to-point ground transport, priced per vehicle.
- Coverage
- Planned through ground-handling aggregators and direct DMC contracts. No coverage claim until the first contract.
- Endpoints
- 3
- Auth
- OAuth 2.0
Activities API
Activities
Tours, tickets and experiences with session-level availability.
- Coverage
- Planned through experience aggregators and direct DMC product. No coverage claim until the first contract.
- Endpoints
- 3
- Auth
- OAuth 2.0
Car rental API
Cars
Vehicle rental search and booking with clear inclusion terms.
- Coverage
- Planned through rental aggregators. No coverage claim until the first contract.
- Endpoints
- 2
- Auth
- OAuth 2.0
Packages API
Packages
Component-based packages priced from live component cost.
- Coverage
- Composed from whatever product APIs your account has enabled.
- Endpoints
- 2
- Auth
- OAuth 2.0
Conventions
The rules every TravelCore API follows
Consistency across products is worth more than cleverness inside any one of them.
OAuth 2.0 client credentials
Short-lived bearer tokens, scoped per capability. Cache them; they last 15 minutes.
Idempotency on every write
State-changing calls require an Idempotency-Key. Replays return the original result.
Partial results, never silent gaps
Slow suppliers are reported per supplier and the response is marked partial.
Structured, not prose
Cancellation policies, fare rules and price breakdowns are objects with fields, not sentences.
Errors you can branch on
A stable machine code, a human message, and a request id you can quote to support.
Webhooks with replay
Signed deliveries, retries with backoff, and an endpoint to inspect past attempts.