Historical airport departure data via FlightAware AeroAPI, pay-per-request at $0.04/call.
What it does
This endpoint returns historical departure flights for a specific airport, sourced from FlightAware's AeroAPI via the StableTravel proxy. You provide an ICAO or IATA airport code as a path parameter (`:id`) and receive a paginated list of past departures including flight ident, operator, origin/destination details, scheduled/actual times, delays, aircraft type, route distance, gates, terminals, and status. Optional query parameters include `airline` (filter by IATA airline code), `start`/`end` (ISO 8601 time range), `max_pages`, and `cursor` for pagination.
The endpoint costs $0.04 per request, paid automatically via MPP (Tempo method on chain 4217) or x402 protocol using USDC — no API keys, OAuth, or subscriptions required. Payment serves as authentication. The response schema includes a `departures` array of flight objects and pagination `links`/`num_pages` fields.
This is part of the broader StableTravel API suite which covers flights (search, book, price, seatmaps via Amadeus), hotels, activities, transfers, Google Flights price comparison, and a full FlightAware integration for real-time tracking, airport info, weather, disruption counts, and flight history. All endpoints follow the same pay-per-request model.
Capabilities
Use cases
- —Analyzing historical departure patterns and on-time performance for a specific airport
- —Building delay analytics dashboards using past departure data
- —Researching airline operational history at a given airport over a date range
- —Auditing flight schedules vs actual departure times for compliance or reporting
- —Feeding historical departure data into ML models for delay prediction
Fit
Best for
- —Agents needing historical airport departure records without managing FlightAware API keys
- —Aviation analytics applications requiring programmatic access to past flight data
- —Travel research tools that need departure history filtered by airline or time range
Not for
- —Real-time departure boards — use the live departures endpoint instead
- —Booking flights — use the Amadeus flight search/book endpoints
- —Bulk historical data dumps spanning months — pagination and per-call cost may add up
Quick start
# Get historical departures from JFK
npx agentcash fetch "https://stabletravel.dev/api/flightaware/history/airports/KJFK/flights/departures"Example
Response
{
"links": {
"next": null
},
"num_pages": 1,
"departures": [
{
"ident": "UAL123",
"origin": {
"city": "New York",
"code": "KJFK",
"name": "John F Kennedy Intl",
"code_iata": "JFK"
},
"status": "Arrived",
"operator": "UAL",
"actual_out": "2025-01-15T08:12:00Z",
"ident_iata": "UA123",
"destination": {
"city": "Los Angeles",
"code": "KLAX",
"name": "Los Angeles Intl",
"code_iata": "LAX"
},
"fa_flight_id": "UAL123-1234567890-schedule-0000",
"aircraft_type": "B739",
"operator_iata": "UA",
"scheduled_out": "2025-01-15T08:00:00Z",
"route_distance": 2475,
"departure_delay": 720
}
]
}Endpoint
Quality
Full OpenAPI 3.1 schema with detailed response types, clear pricing ($0.04/call in USD), live MPP 402 challenge captured, comprehensive documentation with parameter descriptions and endpoint tables. Only minor gap: no inline example response in the spec itself.
Citations
- —Endpoint price is $0.04 per requesthttps://stabletravel.dev/openapi.json
- —Payment via MPP Tempo method on chain 4217 or x402, no API keys requiredhttps://stabletravel.dev/openapi.json
- —Optional parameters include airline, start, end, max_pages, cursorhttps://stabletravel.dev/openapi.json
- —Response returns departures array with flight objects, links, and num_pageshttps://stabletravel.dev/openapi.json
- —Part of StableTravel suite covering flights, hotels, activities, transfers, and FlightAware datahttps://stabletravel.dev