/flightaware/flights/history

POST /api/flightaware/flights/history

Price: 10 credits

Get recent and upcoming legs (flight history) for an airline flight number or tail number

How to use it

Get the recent and upcoming legs of a flight by its airline flight number in ICAO form ('UAL1') or a tail number ('N815UA'). Returns one entry per leg with the FlightAware flight id, status, aircraft type, origin and destination airports, and scheduled/estimated/actual gate, takeoff and landing times. Only the most recent legs (roughly the last two weeks) are available; use 'count' to limit how many are returned.

Parameters

• access-token string required

Request body

• timeout 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) or a tail number (N815UA) (examples: "UAL1", "N815UA"; minLength: 2)
• count integer required — Maximum number of past and upcoming legs to return (min: 1)

Response

• @type string (default: "FlightawareFlightInstance")
• flight_id string required
• ident string nullable
• status string nullable
• is_cancelled boolean nullable
• is_diverted boolean nullable
• aircraft_type string nullable
• aircraft_type_description string nullable
• origin object nullable
  • @type string (default: "FlightawareAirportRef")
  • icao string nullable
  • iata string nullable
  • name string nullable
  • location string nullable
  • latitude number nullable
  • longitude number nullable
  • gate string nullable
  • terminal string nullable
  • timezone string nullable
• destination object nullable
  • @type string (default: "FlightawareAirportRef")
  • icao string nullable
  • iata string nullable
  • name string nullable
  • location string nullable
  • latitude number nullable
  • longitude number nullable
  • gate string nullable
  • terminal string nullable
  • timezone string nullable
• gate_departure object nullable
  • @type string (default: "FlightawareTimes")
  • scheduled_at integer nullable
  • estimated_at integer nullable
  • actual_at integer nullable
• gate_arrival object nullable
  • @type string (default: "FlightawareTimes")
  • scheduled_at integer nullable
  • estimated_at integer nullable
  • actual_at integer nullable
• takeoff object nullable
  • @type string (default: "FlightawareTimes")
  • scheduled_at integer nullable
  • estimated_at integer nullable
  • actual_at integer nullable
• landing object nullable
  • @type string (default: "FlightawareTimes")
  • scheduled_at integer nullable
  • estimated_at integer nullable
  • actual_at integer nullable
• url 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 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.

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.