# StableTravel FlightAware Historical Airport-to-Airport Flights

> StableTravel FlightAware Historical Airport-to-Airport Flights is a paid API for AI agents from StableTravel at stabletravel.dev, paid per call via MPP, $0.24/call, status unknown (last checked 2026-09-14).

Retrieves historical flight records between two specific airports using FlightAware data

## Facts

- Endpoint: GET https://stabletravel.dev/api/flightaware/history/airports/:id/flights/to/:dest_id
- Price: $0.24/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Provider: StableTravel
- Docs: https://stabletravel.dev
- Website: https://stabletravel.dev
- Tags: amadeus, flightaware, flights, hotels, activities, transfers, travel, data, web
- Canonical page: https://www.zero.xyz/c/stabletravel-dest-id-42836458
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_t9iKOuxLOoR_s_XflKgA-

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability stabletravel-dest-id-42836458
```

Example prompt: Can you pull up the historical flights between JFK and LAX using FlightAware, looking within the bounding box from latitude 25 to 50 north and longitude -125 to -65 west, and give me up to 100 results?

## When to prefer this

Use this endpoint when you need historical flight data specifically between two airports (origin and destination pair) via FlightAware. Prefer this over the general airport flights endpoint when you need route-specific history rather than all flights at a single airport. Choose this when building route analysis, historical traffic studies, or verifying past flight operations between two specific airports.

## Known failure modes

- Invalid airport ID returns 404 or empty results
- Missing required bounding box parameters (north/west/south/east) returns 400 validation error
- Invalid coordinate values outside valid lat/lon ranges return error
- No historical flights found for the given route returns empty list
- Service unavailable from FlightAware upstream returns 503

## How this service works

Get historical flights between airports

## Output

A list of historical flight records between the specified origin and destination airports, filtered by the geographic bounding box, including flight details such as flight identifiers, times, and route information sourced from FlightAware.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "north",
  "west",
  "south",
  "east"
 ],
 "properties": {
  "max": {
   "type": "number",
   "description": "Maximum number of results (default 50)"
  },
  "east": {
   "type": "number",
   "description": "Eastern longitude boundary"
  },
  "west": {
   "type": "number",
   "description": "Western longitude boundary"
  },
  "north": {
   "type": "number",
   "description": "Northern latitude boundary"
  },
  "south": {
   "type": "number",
   "description": "Southern latitude boundary"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/stabletravel-dest-id-42836458/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from stabletravel.dev](https://www.zero.xyz/host/stabletravel.dev/llms.txt)