Flightradar24
Live flight tracking, flight history, and airport data from Flightradar24, served as plain REST.
Endpoints
| Endpoint | Path params | Query params | What it returns | Price | Data up to |
|---|---|---|---|---|---|
GET /fr24/live-feed |
— | north, south, west, east, limit, maxage |
Live aircraft positions in a bounding box. | $0.005 | 5 sec |
GET /fr24/top-flights |
— | limit |
Most-tracked flights right now. | $0.003 | 15 sec |
GET /fr24/flight-details |
— | flight_id |
Full detail for one live flight. | $0.005 | 5 sec |
GET /fr24/playback |
— | north, south, west, east, timestamp, limit |
Historical aircraft positions at a past timestamp. | $0.005 | 1 hr |
GET /fr24/flights-status |
— | flight_ids |
Live status for a list of flight ids. | $0.003 | 5 sec |
GET /fr24/nearest-flights |
— | lat, lon, radius, limit |
Live flights nearest a coordinate. | $0.003 | 5 sec |
GET /fr24/search |
— | query, limit |
Search flights, airports, and airlines. | $0.003 | 5 min |
GET /fr24/flight-lookup |
— | flight, history |
Flight history by flight id. | $0.003 | 1 min |
GET /fr24/airport |
— | id, include |
Airport detail (images, weather, stats, runways). | $0.003 | 5 min |
GET /fr24/airport-arrivals |
— | id, page |
Airport arrivals board. | $0.003 | 1 min |
GET /fr24/airport-departures |
— | id, page |
Airport departures board. | $0.003 | 1 min |
GET /fr24/airport-on-ground |
— | id, page |
Aircraft currently on the ground at an airport. | $0.003 | 30 sec |
GET /fr24/airport-disruptions |
— | continent, period, kind |
Airport delay/disruption listings. | $0.003 | 5 min |
GET /fr24/airlines |
— | — | Airline reference list. | $0.001 | 24 hr |
GET /fr24/airports |
— | — | Airport reference list. | $0.001 | 24 hr |
Prices are per call, paid in USDC with x402. "Data up to" is the cache window: a repeated call inside it returns the same data.
Calling it
# x402: no account or API key. The server answers 402 with payment instructions; an x402 client pays and repeats the request.
curl -i "https://<base-url>/fr24/top-flights?limit=10"
Responses are JSON. Field names follow the upstream source, so a response can be larger than the table above suggests.
Notes
airport'sidmust be Flightradar24's internal numeric airport id (e.g.631), not an IATA code — get it fromsearch.flight-lookup'sflightis a hex flight id from asearchresult, not a flight number.- Live endpoints are backed by Flightradar24's own gRPC feed; REST endpoints (airports, search, flight lookup) are its mobile API.
