/google/flights/calendar

POST /api/google/flights/calendar

Price: 20 credits

Get a price grid of departure and return date combinations around the selected round-trip dates

How to use it

Round-trip price calendar between an origin and destination airport (IATA codes). Provide the centre depart_date and return_date; returns a grid of nearby departure and return date combinations, each with the lowest total price and currency, so you can spot the cheapest dates to fly.

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 required — Return date in YYYY-MM-DD format (examples: "2026-07-22")
• count integer required — Maximum number of date combinations to return (min: 1)

Response

• @type string (default: "GoogleFlightsCalendarCell")
• depart_date string required
• return_date string required
• price number nullable
• currency string (default: "USD")

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 price grid available for the given route and dates 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.