/hopper/flights/search

POST /api/hopper/flights/search

Price: 20 credits

Search Hopper flights between an origin and destination (IATA airport codes or city codes) for a departure date, and a return date for round trips, for a given passenger mix (adults, children, seat infants, lap infants). Optionally filter by airlines, maximum stops and maximum price, and choose the ordering. Returns flight itineraries, each with the cheapest total price (base fare and taxes/fees), currency, the outbound and return slices (origin, destination, departure and arrival times, duration, stops and per-segment airline and flight number), and the list of available fare brands with their prices, cabin and remaining seats. Resolve codes via the locations search (kind=flight).

How to use it

Search flights: origin/destination (IATA or city code + origin_type/destination_type), departure_date, return_date (round trips), trip_type, passenger counts (adults/children/seat_infants/lap_infants). Filters: airlines, max_stops, max_price, sort. Each itinerary has trip_id, price (cheapest), base_amount, taxes_and_fees, currency, outbound and inbound slices (segments with airlines, flight numbers, times), and fares (fare brands with price, cabin, available_seats).

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 (resolve via locations search kind=flight) (examples: "BOS"; minLength: 1)
• destination string required — Destination IATA airport code or city code (examples: "LAX"; minLength: 1)
• departure_date string required — Outbound departure date (format: date; examples: "2026-08-15")
• return_date string nullable — Return date (required for round trips) (format: date; examples: "2026-08-18")
• 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")
• adults integer — Number of adult passengers (default: 1; min: 1; max: 9)
• children integer — Number of child passengers (2-11 years) (default: 0; min: 0; max: 8)
• seat_infants integer — Number of infants in their own seat (default: 0; min: 0; max: 8)
• lap_infants integer — Number of infants on lap (default: 0; min: 0; max: 8)
• airlines array — Keep only itineraries whose outbound is operated by these airline codes (e.g. UA, B6) (default: [])
• max_stops integer nullable — Maximum number of stops per slice (min: 0)
• max_price number nullable — Maximum total price (min: 0)
• sort string — Result ordering (default: "recommended"; one of: "recommended", "price_low", "price_high")
• count integer required — Max number of itineraries to return (min: 1)

Response

• @type string (default: "HopperFlightItinerary")
• trip_id string required
• price number nullable
• base_amount number nullable
• taxes_and_fees number nullable
• currency string nullable
• outbound object nullable
  • @type string (default: "HopperFlightSlice")
  • origin string nullable
  • destination string nullable
  • departure string nullable
  • arrival string nullable
  • duration_minutes integer nullable
  • stops integer nullable
  • segments array (default: [])
    • @type string (default: "HopperFlightSegment")
    • origin string nullable
    • destination string nullable
    • marketing_airline string nullable
    • operating_airline string nullable
    • flight_number string nullable
    • departure string nullable
    • arrival string nullable
    • duration_minutes integer nullable
    • layover_minutes integer nullable
• inbound object nullable
  • @type string (default: "HopperFlightSlice")
  • origin string nullable
  • destination string nullable
  • departure string nullable
  • arrival string nullable
  • duration_minutes integer nullable
  • stops integer nullable
  • segments array (default: [])
    • @type string (default: "HopperFlightSegment")
    • origin string nullable
    • destination string nullable
    • marketing_airline string nullable
    • operating_airline string nullable
    • flight_number string nullable
    • departure string nullable
    • arrival string nullable
    • duration_minutes integer nullable
    • layover_minutes integer nullable
• fares array (default: [])
  • @type string (default: "HopperFlightFare")
  • brand_name string nullable
  • cabin string nullable
  • available_seats integer nullable
  • price number nullable
  • base_amount number nullable
  • taxes_and_fees number nullable
  • currency 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 flights found for this 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.