Skip to Content
ResourcesIntegrationsSearch ToolsGoogle Flights

Google Flights

Service domainTRAVEL
Google Flights icon
Arcade OptimizedBYOCPro

Arcade.dev LLM tools for getting flights via Google Flights

Author:Arcade
Version:4.1.0
Auth:No authentication required
4tools
4require secrets

Google Flights Toolkit

The Google Flights toolkit wraps the SerpApi Google Flights endpoint, enabling LLMs and agents to search real-time flight data, resolve itineraries to booking vendors, and look up airport codes — all without requiring user authentication.

Capabilities

  • Airport lookup: Resolve city names, country names, or airport names to IATA codes; supports metropolitan area codes (NYC, LON, etc.) that fan out across all airports in a metro.
  • One-way & round-trip search: Search flights with a single call; round-trip fares are priced as a bundle (not two summed one-ways) and results include direct Google Flights booking URLs.
  • Multi-city / open-jaw search: Query complex itineraries in one call — yields a bundled price that is typically cheaper than equivalent summed one-way searches.
  • Booking option resolution: Convert a booking_token from a search result into a list of airlines and OTAs selling that specific itinerary, with optional POST data for backend vendor hand-offs.

Secrets

SERP_API_KEY — An API key issued by SerpApi, the service that powers the Google Flights data. To obtain one:

  1. Create or log in to an account at serpapi.com.
  2. Navigate to your dashboard — your API key is displayed at the top of the page.
  3. SerpApi has a free tier with limited monthly searches; paid plans are required for higher volume. The key does not require any additional scope configuration — it grants access to all SerpApi engines including Google Flights.

Store the key in Arcade as a secret named exactly SERP_API_KEY. See the Arcade secrets docs for configuration details, or add it directly via the Arcade secrets dashboard.

Available tools(4)

4 of 4 tools
Operations
Behavior
Tool nameDescriptionSecrets
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
Last updated on