/google/flights/search

POST /api/google/flights/search

Price: 5 credits

Search flight itineraries between two airports for a date with optional return, cabin, and stops

How to use it

Search flights between an origin and destination airport (IATA codes) for a departure date. Provide return_date for round-trip itineraries (price is the round-trip total). Filter by cabin (economy, premium_economy, business, first), stops (any, nonstop), and number of adults. Returns ranked itineraries with total price, airline, departure and arrival times, duration, number of stops, layover airports, per-segment flight details, and CO2 emissions.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• origin string required — Origin airport or city IATA code (examples: "JFK", "LAX", "LON"; pattern: ^[A-Za-z]{3}$)
• destination string required — Destination airport or city IATA code (examples: "LAX", "JFK", "CDG"; pattern: ^[A-Za-z]{3}$)
• depart_date string required — Outbound date in YYYY-MM-DD format (examples: "2026-07-15")
• return_date string nullable — Return date in YYYY-MM-DD format; provide it to search round-trip itineraries
• adults integer — Number of adult passengers (default: 1; min: 1; max: 9)
• cabin string — Cabin class (default: "economy"; one of: "economy", "premium_economy", "business", "first")
• stops string — Maximum number of stops (default: "any"; one of: "any", "nonstop")
• count integer required — Maximum number of itineraries to return (min: 1)

Response

• @type string (default: "GoogleFlightsItinerary")
• price number nullable
• currency string (default: "USD")
• airline string nullable
• carrier string nullable
• origin string required
• destination string required
• departure_at string nullable
• arrival_at string nullable
• duration_minutes integer nullable
• stops integer (default: 0)
• layovers array (default: [])
  • @type string (default: "GoogleFlightsLayover")
  • airport string required
  • name string nullable
  • city string nullable
  • duration_minutes integer nullable
• segments array (default: [])
  • @type string (default: "GoogleFlightsSegment")
  • carrier string nullable
  • flight_number string nullable
  • airline string nullable
  • origin string required
  • origin_name string nullable
  • destination string required
  • destination_name string nullable
  • departure_at string nullable
  • arrival_at string nullable
  • duration_minutes integer nullable
  • aircraft string nullable
  • legroom string nullable
• co2_grams integer nullable
• co2_typical_grams integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No flights found for the given route and date Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.