/flightradar24/flights/search

POST /api/flightradar24/flights/search

Price: 1 credit

Find live aircraft currently flying within a geographic area (bounding box)

How to use it

Find live aircraft currently within a geographic bounding box defined by north/south latitude and west/east longitude. Returns one entry per aircraft with its live position (latitude, longitude, altitude, ground speed, track/heading, vertical speed), Mode-S hex, registration, aircraft type, callsign, flight number, origin and destination airport IATA codes, airline ICAO, on-ground flag, and the data source (radar). Toggle the source and category flags (adsb/mlat/flarm/faa/satellite/estimated/air/ground/vehicles/gliders) to narrow what is returned. Use 'count' to cap how many aircraft come back. Use the flight id with the 'flights' endpoint to get full details and the flight track.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Maximum number of aircraft to return (min: 1)
• north number required — Northern bound latitude of the search area (min: -90; max: 90)
• south number required — Southern bound latitude of the search area (min: -90; max: 90)
• west number required — Western bound longitude of the search area (min: -180; max: 180)
• east number required — Eastern bound longitude of the search area (min: -180; max: 180)
• adsb boolean — Include ADS-B tracked aircraft (default: true)
• mlat boolean — Include MLAT (multilateration) tracked aircraft (default: true)
• flarm boolean — Include FLARM tracked aircraft (default: true)
• faa boolean — Include FAA data feed aircraft (default: true)
• satellite boolean — Include satellite (space-based ADS-B) tracked aircraft (default: true)
• estimated boolean — Include aircraft with estimated positions (default: true)
• air boolean — Include airborne aircraft (default: true)
• ground boolean — Include aircraft on the ground (default: true)
• vehicles boolean — Include ground service vehicles (default: true)
• gliders boolean — Include gliders (default: true)

Response

• @type string (default: "Flightradar24LiveFlight")
• id string required
• hex string nullable
• latitude number nullable
• longitude number nullable
• track integer nullable
• altitude integer nullable
• ground_speed integer nullable
• squawk string nullable
• radar string nullable
• aircraft_type string nullable
• registration string nullable
• timestamp integer nullable
• origin_iata string nullable
• destination_iata string nullable
• flight_number string nullable
• is_on_ground boolean nullable
• vertical_speed integer nullable
• callsign string nullable
• airline_icao 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 — The entity was not found, or a precondition failed 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.