Route Detection
Which route endpoint should you call — callsign resolution, airport route list, or route-pair statistics? Route endpoints use SkyLink's own database of routes to map callsigns (flight identifiers on ADS-B, e.g. BAW178) to city pairs and expose airport route lists with frequency statistics.
| Endpoint | Page | When to use |
|---|---|---|
GET /routes/callsign/{callsign} | Callsign → Route | Map a live callsign to departure/arrival airports |
GET /routes/airport/{code} | Airport Routes | List all routes from or to an airport |
GET /routes/pairs | Route Pairs | Query route-pair stats — airlines, distance, typical block time |
Choosing an endpoint. Start with Callsign → Route when you have a live ADS-B callsign and need a city pair. Use Airport Routes to enumerate departures or arrivals at a hub. Use Route Pairs when you already know one or both airport codes and want carrier and distance context.
After resolving airports, chain to Airports for runway data or Distance for precise great-circle calculations. For live flight status, see Flight Status.
Error responses
Shared platform errors: Error Handling. Endpoint-specific:
422 — validation error
Returned when path or query parameters fail schema validation (for example limit outside 1–500).
{
"detail": [
{
"type": "greater_than_equal",
"loc": ["query", "limit"],
"msg": "Input should be greater than or equal to 1"
}
]
}Per-endpoint parameter tables and response fields are on the reference pages linked above.
Related: Flight Status · Schedules · Distance