https://api.sandbase.ai/v1/api/flightradar24/flightsGet live flights from Flightradar24 by airport, flight number, airline, aircraft type or map bounds, with position, altitude, speed, route and aircraft.
Your output will appear here
Complete the inputs, then click Run.
Get live flights from Flightradar24 by airport, flight number, airline, aircraft type or map bounds, with position, altitude, speed, route and aircraft.
curl -X POST "https://api.sandbase.ai/v1/api/flightradar24/flights" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"airport": "AUS"}'
The result is returned in outputs[0].data as structured JSON.
| Name | Type | Required | Description |
|---|---|---|---|
airport | string | No | Parameter defines the airport that flights depart from or arrive at, as a 3-letter IATA airport code (e.g., LHR for London Heathrow). You can search for it on Flightradar24 or IATA. Multiple airports can be separated by commas (e.g., `LHR |
map_bounds | string | No | Parameter defines the GPS coordinates of the map area to search in, like moving the map on Flightradar24. Only flights within these bounds are returned. Its value must be 4 comma-separated numbers matching the following format: north + `, |
flight_number | string | No | Parameter defines the flight number to search for (e.g., BA285). Flights whose number starts with this value are returned, so BA28 also returns BA285 and BA287. Multiple flight numbers can be separated by commas (e.g., BA285,BA287 |
callsign | string | No | Parameter defines the callsign to search for (e.g., BAW5L). A callsign can differ from the flight number: BA285 flies as BAW5L. Flights whose callsign starts with this value are returned. Multiple callsigns can be separated by commas |
airline | string | No | Parameter defines the airline to search for, as a 3-letter ICAO airline code (e.g., BAW for British Airways), not its 2-letter IATA code (BA). The ICAO code is shown after the IATA code when you search for the airline on Flightradar24. |
registration | string | No | Parameter defines the aircraft registration to search for (e.g., G-XLEK). Aircraft whose registration starts with this value are returned, so G-XLE returns the British Airways Airbus A380s, and G- returns every aircraft registered in |
aircraft_type | string | No | Parameter defines the aircraft type to search for, as an ICAO aircraft type designator (e.g., A388 for the Airbus A380-800). It's shown in the aircraft details of a flight on Flightradar24. Aircraft whose type starts with this value are r |
departure_id | string | No | Parameter defines the airport that flights depart from, as a 3-letter IATA airport code (e.g., LHR for London Heathrow). You can search for it on Flightradar24 or IATA. Multiple airports can be separated by commas (e.g., LHR,LGW). |
arrival_id | string | No | Parameter defines the airport that flights arrive at, as a 3-letter IATA airport code (e.g., JFK for New York JFK). You can search for it on Flightradar24 or IATA. Multiple airports can be separated by commas (e.g., JFK,EWR). |
json_restrictor | string | No | Parameter defines the fields you want to include in the output, reducing payload size for faster response. See the JSON Restrictor documentation for more details. |
$0.010 per successful call. Failed calls are not charged.
Start building
Platform API endpoint with unified authentication and usage tracking.
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
-X POST "https://api.sandbase.ai/v1/api/flightradar24/flights" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"airport": "AUS"
}
SANDBASE_JSON
)
printf '%s\n' "$result"Set your SandBase API key in your server environment. Requests use Bearer authentication.
export SANDBASE_API_KEY="YOUR_API_KEY"Keep your key on the server. Do not expose it in browser code.
airportstringParameter defines the airport that flights depart from or arrive at, as a 3-letter IATA airport code (e.g., `LHR` for London Heathrow). You can search for it on Flightradar24 or IATA. Multiple airports can be separated by commas (e.g., `LHR,LGW`).
map_boundsstringParameter defines the GPS coordinates of the map area to search in, like moving the map on Flightradar24. Only flights within these bounds are returned. Its value must be 4 comma-separated numbers matching the following format: `north` + `,` + `east` + `,` + `south` + `,` + `west` `north` and `south` are latitudes, and `east` and `west` are longitudes (e.g., `51.69,0.33,51.28,-0.51` for London). An area crossing the antimeridian has a `west` longitude greater than its `east` longitude (e.g., `60,-170,40,170` around the Aleutian Islands). When not set, flights are searched worldwide. Flightrada
flight_numberstringParameter defines the flight number to search for (e.g., `BA285`). Flights whose number starts with this value are returned, so `BA28` also returns `BA285` and `BA287`. Multiple flight numbers can be separated by commas (e.g., `BA285,BA287`).
callsignstringParameter defines the callsign to search for (e.g., `BAW5L`). A callsign can differ from the flight number: `BA285` flies as `BAW5L`. Flights whose callsign starts with this value are returned. Multiple callsigns can be separated by commas (e.g., `BAW5L,BAW28K`).
airlinestringParameter defines the airline to search for, as a 3-letter ICAO airline code (e.g., `BAW` for British Airways), not its 2-letter IATA code (`BA`). The ICAO code is shown after the IATA code when you search for the airline on Flightradar24. Multiple airlines can be separated by commas (e.g., `BAW,VIR`).
registrationstringParameter defines the aircraft registration to search for (e.g., `G-XLEK`). Aircraft whose registration starts with this value are returned, so `G-XLE` returns the British Airways Airbus A380s, and `G-` returns every aircraft registered in the United Kingdom. Multiple registrations can be separated by commas (e.g., `G-XLEK,G-XLEH`).
aircraft_typestringParameter defines the aircraft type to search for, as an ICAO aircraft type designator (e.g., `A388` for the Airbus A380-800). It's shown in the aircraft details of a flight on Flightradar24. Aircraft whose type starts with this value are returned, so `B77` returns every Boeing 777 variant. Multiple aircraft types can be separated by commas (e.g., `A388,B748`).
departure_idstringParameter defines the airport that flights depart from, as a 3-letter IATA airport code (e.g., `LHR` for London Heathrow). You can search for it on Flightradar24 or IATA. Multiple airports can be separated by commas (e.g., `LHR,LGW`).
arrival_idstringParameter defines the airport that flights arrive at, as a 3-letter IATA airport code (e.g., `JFK` for New York JFK). You can search for it on Flightradar24 or IATA. Multiple airports can be separated by commas (e.g., `JFK,EWR`).
json_restrictorstringParameter defines the fields you want to include in the output, reducing payload size for faster response. See the JSON Restrictor documentation for more details.
Saved example response for this API; no live request is made when viewing it.
No saved response has been published. Run the API in Playground to inspect its response.
Explore more
| API | Price | Response |
|---|---|---|
Flightradar24 Live FlightsThis API Flightradar24 | $0.01 per call | JSON |
Questions
Send a POST request to https://api.sandbase.ai/v1/api/flightradar24/flights with your SandBase API key in the Authorization header (Bearer) and the parameters as a JSON body. You can also try it in the Playground on this page without writing code.
$0.01 per call, billed from your SandBase balance. You are only charged for calls you make; there is no subscription.
No parameters are required. Optional: airport (string), map_bounds (string), flight_number (string), callsign (string), airline (string) and registration (string) and 4 more. The Parameters table and the Playground on this page list every field.
A JSON response returned in the same HTTP request (synchronous).
No. Flightradar24 Live Flights runs through SandBase, so one SandBase API key covers this endpoint and every other API and model in the catalog. You do not need to apply for Flightradar24 API access separately.