Google Flights
Service domainTRAVEL
Arcade OptimizedBYOCPro
Arcade.dev LLM tools for getting flights via Google Flights
Author:Arcade
Version:
4.1.0Auth:No authentication required
4tools
4require secrets
Google Flights Toolkit
The Arcade Google Flights toolkit enables LLMs to search, compare, and resolve flight itineraries via the SerpApi Google Flights API — covering one-way, round-trip, multi-city, and booking-option lookups.
Capabilities
- Airport discovery: Resolve city names, country names, or airport names to IATA codes, including metropolitan codes (NYC, LON, TYO, PAR) that span multiple airports.
- One-way & round-trip search: Query Google Flights for itineraries in a single call; round-trip fares are priced independently from summed one-ways, so a combined call is required for accurate pricing.
- Multi-city / open-jaw search: Search bundled multi-leg itineraries that are typically cheaper than equivalent summed one-way queries.
- Booking-option resolution: Resolve a
booking_tokenfrom any flight search to the airlines and OTAs selling that specific itinerary, with optional POST data for backend vendor hand-off. - Direct booking links: Every search result includes a
google_flights_urlthat opens the pre-selected itinerary on Google Flights, so users can be handed a booking link without an additional lookup.
Secrets
SERP_API_KEY — An API key issued by SerpApi, the service that powers the underlying Google Flights data. To obtain one:
- Create or log in to an account at https://serpapi.com/users/sign_up.
- Navigate to your SerpApi dashboard — your API key is displayed on the dashboard home page under Your Private API Key.
- SerpApi requires a paid or trial plan to make live requests; free-tier accounts have a limited monthly search quota. Ensure your plan supports the Google Flights engine (
google_flights). - Copy the key and register it as a secret in Arcade.
See the SerpApi API Key docs for key management and rotation details.
For configuring secrets in Arcade, see the Arcade secrets guide. You can also manage secrets directly at https://api.arcade.dev/dashboard/auth/secrets.
Available tools(4)
4 of 4 tools
Operations
Behavior
| Tool name | Description | Secrets | |
|---|---|---|---|
Resolve a ``booking_token`` to the airlines and OTAs selling that itinerary.
Pass a ``booking_token`` returned by ``search_flights`` or
``search_multi_city_flights`` to get the vendors selling that
specific flight. The token encodes the route, dates, cabin class,
and passenger counts (every segment for multi-city), so there are
no ``travel_class``, ``num_adults``, or ``num_children`` parameters;
supplying a cabin or party size would silently disagree with the
itinerary the token was issued for.
Leave ``include_booking_post_data`` off (the default) when an LLM
is comparing prices; turn it on only when a backend needs to
rebuild the vendor hand-off, since the POST body is multiple
kilobytes per option. | 1 | ||
Find IATA airport codes for a city, country, or airport name.
Metropolitan codes (NYC, LON, TYO, PAR, ...) are accepted as a
``departure_airport_code`` or ``arrival_airport_code`` in flight
searches and mean "any airport in this city". | 1 | ||
Search Google Flights for one-way or round-trip itineraries.
For a trip where the traveler returns to their origin, issue a
single call with both ``outbound_date`` and ``return_date`` set.
Do NOT issue two separate one-way searches in opposite directions
and sum the prices: airlines price round-trip fares independently
from one-way fares, so the sum of two cheapest one-ways is rarely
equal to the cheapest round-trip and is typically more expensive.
Each returned itinerary carries a ``google_flights_url`` that opens
that specific pre-selected flight on Google Flights, so you can hand
the user a booking link straight from these results without a
separate booking-options lookup. | 1 | ||
Search Google Flights for a multi-city (open-jaw) itinerary.
Use this for trips that are neither a simple one-way nor a round-trip
(e.g. an open-jaw three-leg trip that ends back at the origin).
The open-jaw bundle is typically cheaper than the equivalent set
of one-way searches summed; never substitute multiple
``search_flights`` calls for a single multi-city query.
Each returned itinerary carries a ``google_flights_url`` that opens
that specific pre-selected itinerary on Google Flights, so you can
hand the user a booking link straight from these results without a
separate booking-options lookup. | 1 |
Get Building
Last updated on