Flights API
Flight API
Schedules, fares, availability and ticketing through one normalised interface.
The Flight API is specified against the same conventions as the Hotel API: an offer-and-order model, server-side pricing rules, and a re-validation step before payment. It is architected and documented, and not yet built. Air is materially harder than hotels because ticketing, changes and refunds are governed by fare rules that vary per carrier, and we would rather ship it late than ship it wrong.
Coverage
Planned via GDS and NDC aggregation. No coverage claim is made until the first carrier or aggregator contract is signed.
Latency behaviour
Target parity with the hotel search budget once implemented. No commitment is published before the first live route.
Authentication
Capabilities
- One-way, return and multi-city search
- Branded fares and ancillary display
- Offer re-pricing before ticketing
- Order creation, ticketing and void window handling
- Structured fare rules rather than free text
What it does not do
- — Not implemented. Sandbox responses are illustrative only and do not represent a live carrier.
- — Changes, refunds and involuntary reaccommodation are the hardest parts and will be delivered after the booking path.
Reference
Endpoints
The full surface, with real request and response shapes where the endpoint is implemented.
/v1/flights/searchSearch offers across connected sources.
/v1/flights/offers/{offerId}/priceRe-price an offer immediately before order creation.
/v1/flights/ordersIdempotency-Key requiredCreate an order from a priced offer.
/v1/flights/orders/{orderId}Retrieve an order and its ticketing state.
/v1/flights/orders/{orderId}/cancelIdempotency-Key requiredCancel or void within the permitted window.