POST /api/flightradar24/airports
Price: 1 credit
Get airport details, delay statistics and location by IATA or ICAO code
Get details for an airport by its IATA (3-letter, e.g. 'lax') or ICAO (4-letter, e.g. 'klax') code. Returns the airport name, position (latitude, longitude, elevation), city, country, timezone, arrival and departure delay indices, on-time/delayed/canceled counts for arrivals and departures today, the number of aircraft currently on the ground, homepage/webcam/Wikipedia links, and photos. Use 'airports/schedule' for the live departures/arrivals board and 'airports/routes' for served destinations.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)code string required — Airport IATA (3-letter) or ICAO (4-letter) code (examples: "lax", "klax", "lhr")@type string (default: "Flightradar24AirportDetail")name string requirediata string nullableicao string nullablelatitude number nullablelongitude number nullableelevation integer nullablecity string nullablecountry string nullablecountry_code string nullabletimezone string nullabletimezone_offset integer nullabletimezone_abbr string nullabledelay_index_arrivals number nullabledelay_index_departures number nullablearrivals object nullable@type string (default: "Flightradar24AirportStats")delay_index number nullabledelay_avg number nullableon_time_today integer nullabledelayed_today integer nullablecanceled_today integer nullabledepartures object nullable@type string (default: "Flightradar24AirportStats")delay_index number nullabledelay_avg number nullableon_time_today integer nullabledelayed_today integer nullablecanceled_today integer nullableaircraft_on_ground integer nullablehomepage_url string nullablewebcam_url string nullablewikipedia_url string nullableimages array (default: [])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 airport found for the given code 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.