/skyscanner/flights/prices/calendar

POST /api/skyscanner/flights/prices/calendar

Price: 1 credit

Get the cheapest available flight price for each day over the coming year for a route between two places (identified by their Skyscanner sky ids). Returns a day-by-day calendar with the lowest price, currency and a relative price tier (low, medium or high) for each date, letting you spot the cheapest days to fly. Resolve the origin and destination sky ids from the places search endpoint.

How to use it

Cheapest flight price per day for a route between two Skyscanner sky ids (origin, destination, e.g. NYCA, LOND — resolve via places/search). Returns a list of days, each with date, price, currency and price_tier (low/medium/high relative cheapness). Use count to cap how many upcoming days to return.

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 sky id (resolve via places search) (examples: "NYCA"; minLength: 2)
• destination string required — Destination sky id (resolve via places search) (examples: "LOND"; minLength: 2)
• count integer required — Max number of days to return (min: 1)

Response

• @type string (default: "SkyscannerFlightPriceCalendarDay")
• date string nullable
• price number nullable
• currency string nullable
• price_tier string 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 price calendar available for the given route (unknown sky id or no flights on the route) 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.