/flightaware/airports

POST /api/flightaware/airports

Price: 10 credits

Get airport details (location, elevation, runways, timezone, delay status) by IATA or ICAO code

How to use it

Get reference details for an airport by its IATA (3-letter, e.g. 'SFO') or ICAO (4-letter, e.g. 'KSFO') code. Returns the airport name, city/state, coordinates, elevation (feet and meters), timezone, owner, available fuel types, the list of runways (name, dimensions, surface, condition, lighting), a Wikipedia link and the current delay status when the airport is experiencing delays. Use 'airports/arrivals', 'airports/departures', 'airports/enroute' and 'airports/scheduled' for the live flight boards.

Parameters

• access-token string required

Request body

• timeout 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: "SFO", "KSFO", "LHR")

Response

• @type string (default: "FlightawareAirport")
• icao string nullable
• iata string nullable
• name string required
• location string nullable
• latitude number nullable
• longitude number nullable
• elevation_ft number nullable
• elevation_m number nullable
• timezone string nullable
• owner string nullable
• fuel_types array (default: [])
• runways array (default: [])
  • @type string (default: "FlightawareRunway")
  • name string nullable
  • dimensions string nullable
  • surface string nullable
  • condition string nullable
  • lighting string nullable
• wikipedia_url string nullable
• delay_status 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 — 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.

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.