Flight Schedule API: Departures and Arrivals by Airport IATA

A “flight API” is useless if it only gives you a map pin. Most products need the board: what is leaving JFK, what actually pushed, which gate, is it delayed.

That is the FlightLabs flights-schedules endpoint. Pass an airport IATA code and type=departure or arrival. The sample below is a live pull from 16 Sep 2026 for JFK departures (truncated to one flight). Interactive docs: api.goflightlabs.com/flights-schedules.

Flight schedule API request

curl "https://api.goflightlabs.com/flights-schedules?access_key=YOUR_ACCESS_KEY&iataCode=JFK&type=departure"

Required: iataCode. Optional filters from the docs: type (departure or arrival), airline_iata (e.g. AA), airline_icao, flight_iata, flight_icao, plus limit / skip for pagination.

This is the public /flights-schedules URL (airport timetable). It is not the live-map endpoint and not /future-flights (that one predicts a future date from history).

What the flight schedule JSON includes

{
"success": true,
"type": "departure",
"data": [
{
"airline_iata": "TG",
"airline_icao": "THA",
"flight_iata": "TG6173",
"flight_number": "6173",
"dep_iata": "JFK",
"dep_icao": "KJFK",
"dep_terminal": "7",
"dep_gate": "5",
"dep_time": "2026-09-16 13:30",
"dep_time_utc": "2026-09-16 17:30",
"dep_estimated": "2026-09-16 13:19",
"dep_actual": "2026-09-16 13:19",
"arr_iata": "HND",
"arr_icao": "RJTT",
"arr_time": "2026-09-17 16:55",
"status": "active",
"duration": 865,
"cs_airline_iata": "NH",
"cs_flight_iata": "NH109"
}
]
}

Codeshare is in cs_*. The docs list status values such as scheduled, cancelled, and landed; live boards also return active. Times come in local and UTC, scheduled / estimated / actual. That is enough for a delay banner without a second endpoint.

Need American Airlines only?

curl "https://api.goflightlabs.com/flights-schedules?access_key=YOUR_ACCESS_KEY&iataCode=JFK&type=departure&airline_iata=AA"

What a schedule board is for

• Airport / FBO screens. Terminal, gate, dep_estimated / dep_actual, and status are enough for a delay banner without a live-map endpoint.
• Airline ops widgets. Filter airline_iata (the AA curl above). Codeshare sits in cs_* so you can show the marketing flight.
• Not fares, not a radar. Prices are /retrieveFlights. Live positions are a different FlightLabs URL. Cache 1–5 minutes.

Go live with FlightLabs schedules

Starter is $24.99/mo for 4,000 calls (10 req / 10 sec). Same aviation dataset as higher tiers: live flights, historical, delays, routes, prices. Upgrade only when the quota runs out. Soft Limit (extra usage beyond the plan) is on by default and can be turned off in account settings.

Endpoint page: goflightlabs.com/flights-schedules. Interactive docs: api.goflightlabs.com/flights-schedules.

FAQ: flight schedule API

Is this live aircraft positions?

No. /flights-schedules is the airport timetable (departures/arrivals by IATA). Live tracking is a different FlightLabs endpoint. Predicted future dates are /future-flights.

What do I pass?

Required iataCode (airport). Add type=departure or arrival, and optionally airline_iata / flight_iata.

Which plan includes schedules?

All paid plans list Scheduled Flights. Starter is $24.99/mo, 4,000 calls, 7-day trial (or 50 requests).

Start the 7-day trial →