/flightaware/airports/scheduled

POST /api/flightaware/airports/scheduled

Price: 5 credits

Get the scheduled departures board (not yet airborne) for an airport by IATA or ICAO code

How to use it

Get the scheduled departures board for an airport by IATA (3-letter, e.g. 'SFO') or ICAO (4-letter, e.g. 'KSFO') code. Returns upcoming departures that have not yet taken off, each with its flight identifier, aircraft type, origin and destination airport codes, the destination airport name/IATA, scheduled departure time and the displayed local departure and arrival times. Use 'count' to control how many flights are returned.

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")
• count integer required — Maximum number of flights to return (min: 1)

Response

• @type string (default: "FlightawareBoardFlight")
• ident string required
• aircraft_type string nullable
• origin_code string nullable
• origin_iata string nullable
• origin_name string nullable
• destination_code string nullable
• destination_iata string nullable
• destination_name string nullable
• scheduled_departure_at integer nullable
• departure_time string nullable
• arrival_time string nullable
• url 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.