POST /api/flightaware/flights
Price: 10 credits
Get the current or most recent flight for an airline flight number, tail number, or flight id
Get the current or most recent leg of a flight by its identifier. Accepts an airline flight number in ICAO form (e.g. 'UAL1'), an aircraft tail number (e.g. 'N815UA'), or a specific FlightAware flight id. The IATA flight number (e.g. 'UA1') is not accepted here — use the ICAO form. Returns the flight status (and the IATA flight number as 'iata_ident'), operating airline, aircraft type/model, origin and destination airports (with gate and terminal), scheduled/estimated/actual gate, takeoff and landing times, filed route, altitude, speed and distance, live position (groundspeed, altitude, heading when airborne) and the average departure/arrival delays for the route. The aircraft tail number is not exposed on this page and comes back null. Use 'flights/track' for the flown track and 'flights/history' for past legs.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)ident string required — Flight identifier: airline flight number in ICAO form (UAL1), an aircraft tail number (N815UA), or a specific FlightAware flight id (examples: "UAL1", "N815UA"; minLength: 2)@type string (default: "FlightawareFlight")ident string requirediata_ident string nullablefriendly_ident string nullableflight_id string nullablestatus string nullableis_cancelled boolean nullableis_diverted boolean nullableaircraft object nullable@type string (default: "FlightawareAircraftInfo")type_code string nullabledescription string nullablemanufacturer string nullablemodel string nullableengine_count integer nullableengine_type string nullableis_heavy boolean nullableairline object nullable@type string (default: "FlightawareAirline")name string nullableshort_name string nullableicao string nullableiata string nullablecallsign string nullableurl string nullableorigin object nullable@type string (default: "FlightawareAirportRef")icao string nullableiata string nullablename string nullablelocation string nullablelatitude number nullablelongitude number nullablegate string nullableterminal string nullabletimezone string nullabledestination object nullable@type string (default: "FlightawareAirportRef")icao string nullableiata string nullablename string nullablelocation string nullablelatitude number nullablelongitude number nullablegate string nullableterminal string nullabletimezone string nullablegate_departure object nullable@type string (default: "FlightawareTimes")scheduled_at integer nullableestimated_at integer nullableactual_at integer nullablegate_arrival object nullable@type string (default: "FlightawareTimes")scheduled_at integer nullableestimated_at integer nullableactual_at integer nullabletakeoff object nullable@type string (default: "FlightawareTimes")scheduled_at integer nullableestimated_at integer nullableactual_at integer nullablelanding object nullable@type string (default: "FlightawareTimes")scheduled_at integer nullableestimated_at integer nullableactual_at integer nullablefiled_route string nullablefiled_altitude integer nullablefiled_speed integer nullableplanned_distance integer nullabledistance_flown integer nullabledistance_remaining integer nullableete integer nullablegroundspeed integer nullablealtitude integer nullableheading integer nullableaverage_departure_delay integer nullableaverage_arrival_delay integer 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 flight found for the given identifier 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.