Get a Selected Flight Offer
View all Booking.com Hotel & Travel Data endpoints →Inspect the documented flight-detail route with a token from a selected flight-search offer and optional languageCode. Documentation locates the token in data.flightOffers[].token of ordinary one-way, round-trip, or multi-city search. Treat it as opaque search context, not an account login credential, and never publish or hard-code a captured value. This detail response, token lifetime, price fields, and availability were not live-validated. It does not reserve or purchase flights.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/booking/flights-detail API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/booking/flights-detail?key=<API_KEY>&token=<token>'
Query Result
Use Cases
- Evaluate a detail panel only when a traveler opens a shortlisted flight.
- Carry a selected search-offer token into a read-only itinerary inspection.
- Audit accidental use of a city or airport code in the flight-token input.
- Inspect actual offer conditions before designing a separate ticketing handoff.
Frequently asked questions
Where does token come from?
Documentation identifies data.flightOffers[].token in ordinary one-way, round-trip, or multi-city search. Obtain a selected offer's current value; no static token or lifetime guarantee is provided.
Is token a user account login credential?
It is documented as an opaque flight-offer context token, not an account login. Handle it privately and do not place captured values in shared examples. This detail route was not live-validated.