Future Flights Prediction API


The future flights endpoint returns the stored schedule of one airport for one date after today (UTC), through 12 months ahead. For today's flights use /advanced-flights-schedules; for past dates use /historical.

airline_iata keeps one airline from that stored day. limit (1 to 1000) with page (1-based) or skip returns a slice, plus total and has_more. Send page or skip, not both, and only together with limit. Without limit, a successful response is the whole stored day. Requests that include airline_icao, flight_iata, flight_num, dep_iataCode, dep_icaoCode, arr_iataCode, arr_icaoCode or offset return a 400 error naming the parameter.

NOTE: The Future Flights Endpoint returns the schedules airlines have filed for the requested date, including terminals and IATA codes. A busy airport answers right away with a same-weekday prediction while the filed schedule is collected; a request a few minutes later returns that schedule, including terminals. The stored day is refreshed every 12 to 24 hours, and the previous one keeps answering while the refresh runs. If neither the filed schedule nor the prediction is ready, the endpoint answers 503 with success: false, a Retry-After header and a retry_after field (seconds); ask again after that time. When filed schedules are not available for an airport or date, the prediction is the response; in that case terminal, gate and aircraft fields are null. For more accurate and specific flight details, especially for recent changes or unique flights, consider using the Flight Prices Endpoint.

Example API Request:

Use Edit parameters to customize the call, then run it and review the live response below.

Edit the parameters below. The example request updates as you type.

Airport IATA code.

departure or arrival (case-insensitive).

A date after today (UTC), through 12 months ahead.

Optional. Keeps only this airline from the stored day.

Optional. Page size, 1 to 1000. Omit it to receive the whole day.

Optional, 1-based. Requires limit. Do not send with skip.

Optional offset into the stored day. Requires limit. Do not send with page.

Postman Test In Postman

API Response Objects

Each item in the response data array includes the following fields.

Field Description
sortTime Scheduled time at the requested airport, in UTC (ISO 8601).
departureTime.timeAMPM The local departure time in 12-hour AM/PM format.
departureTime.time24 The local departure time in 24-hour format.
arrivalTime.timeAMPM The local arrival time in 12-hour AM/PM format.
arrivalTime.time24 The local arrival time in 24-hour format.
carrier.fs Airline IATA code (ICAO code only when the airline has no IATA code).
carrier.name The name of the carrier.
carrier.flightNumber The flight number, without the airline code.
carrier.iata Airline IATA code.
carrier.icao Airline ICAO code.
operatedBy For codeshare flights, the operating airline and flight number (e.g. "Operated by Emirates 160"); null otherwise.
isCodeshare true when this row is a codeshare (marketing) flight.
airport.fs IATA code of the other airport: origin for arrivals, destination for departures.
airport.city The city where that airport is located.
flight.iataNumber Flight IATA code-number (e.g. EK222). Same format as flight_iata in the Flights Schedules endpoint.
flight.icaoNumber Flight ICAO code-number (e.g. UAE222).
departure.iataCode Departure airport IATA code.
departure.icaoCode Departure airport ICAO code.
departure.terminal Departure terminal.
departure.gate Departure gate, when already assigned.
arrival.iataCode Arrival airport IATA code.
arrival.icaoCode Arrival airport ICAO code.
arrival.terminal Arrival terminal.
arrival.gate Arrival gate, when already assigned.
aircraft.modelCode Scheduled aircraft type code (e.g. B77W).
aircraft.modelText Scheduled aircraft type name.