POST /api/skyscanner/flights/prices/bands
Price: 1 credit
Get the historical price distribution (price bands) for a flight route between two places by entity id for a given date, cabin class and trip type. Returns the typical price spread — low (20th percentile), median and high (80th percentile) price points plus the lower and upper outlier bounds, all in the market currency, along with the season the aggregation covers. Use it to judge whether a live fare is cheap or expensive versus what this route normally costs. For round trips also pass a return date. Origin and destination are Skyscanner place entity ids (resolve them via the places autosuggest).
Historical price distribution for a flight route between two Skyscanner place entity ids (origin, destination) for a depart_date (and optional return_date for round trips) and cabin_class. Returns price bands with currency, season, percentile_low/percentile_high (e.g. 20/80), and the price points outlier_low, low, median, high, outlier_high. Prices are typical historical values, not a live fare quote.
access-token string requiredtimeout 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+$)depart_date string required — Outbound flight date (format: date; examples: "2026-08-15")return_date string nullable — Return flight date for round trips; omit for one-way (format: date; examples: "2026-08-22")cabin_class string — Cabin class (default: "ECONOMY"; one of: "ECONOMY", "PREMIUM_ECONOMY", "BUSINESS", "FIRST")@type string (default: "SkyscannerPriceBand")vertical string nullablecurrency string nullableseason string nullablepercentile_low integer nullablepercentile_high integer nullableoutlier_low number nullablelow number nullablemedian number nullablehigh number nullableoutlier_high number nullable422 — 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-band history available for the given route, date and cabin combination 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.