/flightaware/flights/search

POST /api/flightaware/flights/search

Price: 10 credits

Find scheduled flights between two airports (route finder)

How to use it

Find the scheduled flights operating between two airports. Provide 'origin' and 'destination' as IATA (3-letter) or ICAO (4-letter) airport codes. Returns one entry per scheduled flight with the operating airline and alliance, aircraft type and tail number, origin/destination gates and terminals, scheduled departure and arrival times, filed route/altitude/speed and estimated time enroute, cabin seat counts and baggage claim. Returns an empty list when no scheduled service is found for the route. Use 'count' to limit how many flights are returned.

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 airport IATA or ICAO code (examples: "SFO", "KSFO")
• destination string required — Destination airport IATA or ICAO code (examples: "LAX", "KLAX")
• count integer required — Maximum number of scheduled flights to return (min: 1)

Response

• @type string (default: "FlightawareScheduledFlight")
• operator string nullable
• airline_icao string nullable
• alliance string nullable
• destination_city string nullable
• aircraft_type string nullable
• registration string nullable
• scheduled_departure_at integer nullable
• scheduled_arrival_at integer nullable
• origin_gate string nullable
• origin_terminal string nullable
• destination_gate string nullable
• destination_terminal string nullable
• route string nullable
• route_distance integer nullable
• filed_altitude integer nullable
• filed_airspeed integer nullable
• filed_ete string nullable
• baggage_claim string nullable
• seats_first integer nullable
• seats_business integer nullable
• seats_coach integer nullable
• status 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 — Could not load the route finder for the given airports 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.