Skip to main content
Flight search is a planning loop: find the airports, compare offers, narrow by cabin and stops, check the cheapest date, look at the seat map, then look again when the dates move. Through AgentKey your agent runs that loop against Booking.com flight data with the same three calls — find_tools, describe_tool, execute_tool. Every operation is a lookup; nothing is ticketed or held.

What you can ask

  • “Cheapest non-stop flights from Shanghai to Singapore on 3 December, returning 10 December.”
  • “Business-class options London to New York next Friday, sorted by fastest.”
  • “Build a multi-city trip: Tokyo to Seoul on the 5th, Seoul to Taipei on the 9th, Taipei to Tokyo on the 14th.”
  • “What’s the lowest economy fare for Paris to Rome on these dates?”
  • “Show the full itinerary for this offer.”
  • “Which seats are still free on this flight, and what do they cost?”
  • “上海到东京 12 月 20 日往返,两个大人一个 5 岁小孩,有哪些航班?”
  • “Which airports serve Milan?”

What’s covered

Airports
  • Search airports by airport name, city, region or country, returning the ids the flight search uses; results in a chosen language
Flight search
  • One-way or return between two airports for a departure date and an optional return date
  • Number of adults and each child’s age; cabin class — economy, premium economy, business or first
  • Sort by best, cheapest or fastest; filter to non-stop, one-stop or two-stop flights, or allow any
  • Prices in a chosen currency; page numbers for long result sets
Multi-city itineraries
  • Any sequence of legs, each with its own origin, destination and date, with the same party, cabin, sort and currency options
Offer details and seats
  • The full details of one offer from its search token
  • The seat map for an offer, with seat prices in a chosen currency
Lowest fares
  • The minimum price for a route and dates, by cabin class, for a single route or for a multi-leg itinerary

How to use it

Pass the request in plain language and let the router pick the tool:
The tools chain: airport search gives ids in the form BOM.AIRPORT, the flight search gives offers with tokens, and the details and seat-map tools take a token. Always describe_tool before executing — multi-city search takes its legs as a list of origin, destination and date.
Building with code? The same capability is available as fixed-contract Scenario Methods: travel.flight.search searches offers between two airports for given dates and returns a normalized offer page, and travel.location.search finds the airports first.

FAQ

No. Search, offer details, seat maps and minimum prices are all read-only. No ticket is issued and no fare is held.
Fetched at request time. Offer tokens belong to the search that produced them — if a details or seat-map call rejects a token, run the search again and use the fresh one.
Prices can be requested in any currency on Booking.com’s currency list; airport search results can be returned in any language on its language list. Both lists are available as lookups (see Attractions and local transport).