/hopper/flights/prices

POST /api/hopper/flights/prices

Price: 5 credits

Get Hopper's flight price calendar between an origin and destination (IATA airport codes or city codes). Returns price buckets that colour-code departure dates by how cheap they are — each bucket has a price label (e.g. $250+), a category (lowest, lower, higher, highest) and the list of dates that fall in that price band, so you can see when it is cheapest to fly. Resolve codes via the locations search (kind=flight).

How to use it

Flight price calendar for origin->destination (IATA or city code + origin_type/destination_type), trip_type. Returns price buckets each with price_label, category (lowest/lower/higher/highest) and dates (list of departure dates in that price band).

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 IATA airport code or city code (examples: "BOS"; minLength: 1)
• destination string required — Destination IATA airport code or city code (examples: "LAX"; minLength: 1)
• trip_type string — Round trip or one way (default: "round_trip"; one of: "round_trip", "one_way")
• origin_type string — Whether origin is an airport (IATA) or a city code (default: "airport"; one of: "airport", "city")
• destination_type string — Whether destination is an airport (IATA) or a city code (default: "airport"; one of: "airport", "city")

Response

• @type string (default: "HopperFlightPriceBucket")
• price_label string nullable
• category string nullable
• dates array (default: [])

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 this 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.