/flightradar24/flights/history

POST /api/flightradar24/flights/history

Price: 5 credits

Get past and upcoming flights for a flight number

How to use it

Get the schedule and history of a flight number (e.g. 'AA100', 'BA286') — every past and upcoming instance of that flight. Returns one entry per flight with its Flightradar24 flight id, aircraft type and registration, operating airline, origin and destination airports, and scheduled/estimated/real departure and arrival times plus status. Use 'count' to control how many instances are returned. Pass a returned flight id to the 'flights' endpoint for full details and the track.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• flight_number string required — Flight number (IATA or ICAO) (examples: "AA100", "BA286"; minLength: 2)
• count integer required — Maximum number of flights to return (min: 1)

Response

• @type string (default: "Flightradar24Flight")
• id string nullable
• flight_number string nullable
• callsign string nullable
• is_live boolean nullable
• status_text string nullable
• status_type string nullable
• aircraft_type string nullable
• aircraft_model string nullable
• registration string nullable
• hex string nullable
• owner_name string nullable
• airline object nullable
  • @type string (default: "Flightradar24Airline")
  • name string nullable
  • iata string nullable
  • icao string nullable
  • short string nullable
• origin object nullable
  • @type string (default: "Flightradar24Airport")
  • name string nullable
  • iata string nullable
  • icao string nullable
  • latitude number nullable
  • longitude number nullable
  • city string nullable
  • country string nullable
  • country_code string nullable
  • timezone string nullable
  • timezone_offset integer nullable
  • terminal string nullable
  • gate string nullable
• destination object nullable
  • @type string (default: "Flightradar24Airport")
  • name string nullable
  • iata string nullable
  • icao string nullable
  • latitude number nullable
  • longitude number nullable
  • city string nullable
  • country string nullable
  • country_code string nullable
  • timezone string nullable
  • timezone_offset integer nullable
  • terminal string nullable
  • gate string nullable
• time object nullable
  • @type string (default: "Flightradar24FlightTime")
  • scheduled_departure_at integer nullable
  • scheduled_arrival_at integer nullable
  • real_departure_at integer nullable
  • real_arrival_at integer nullable
  • estimated_departure_at integer nullable
  • estimated_arrival_at integer 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 the given flight number 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.