/skyscanner/flights/prices/months

POST /api/skyscanner/flights/prices/months

Price: 1 credit

Get the cheapest flight price for each upcoming month between two places by entity id. Returns a calendar of monthly lowest prices (one entry per month for the next year) with the year and month, the cheapest price and currency, and a relative price level (low, lowest) marking the best-value months. Origin and destination are Skyscanner place entity ids (resolve them via the places autosuggest). Prices are indicative lowest fares and change frequently.

How to use it

Cheapest flight price per month between two Skyscanner place entity ids (origin, destination) for a trip_type (round_trip or one_way). Returns one entry per upcoming month with date (YYYY-MM), year, month, price, currency and price_category (LOW / LOWEST for the cheapest months). Use places/search to resolve place names into the entity ids.

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 place entity id (examples: "27537542"; pattern: ^\d+$)
• destination string required — Destination place entity id (examples: "27544008"; pattern: ^\d+$)
• trip_type string — Trip type (default: "ROUND_TRIP"; one of: "ROUND_TRIP", "ONE_WAY")
• count integer required — Max number of months to return (min: 1)

Response

• @type string (default: "SkyscannerMonthPrice")
• date string nullable
• year integer nullable
• month integer nullable
• price number nullable
• currency string nullable
• price_category 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 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.