FlightTrackerLED API Sign in

API reference · version 1

Flight Route API documentation

The API answers one question well: where is this flight coming from and going to? Send a callsign, get the route as JSON.

Base URL
https://www.flighttrackerled.com/api/v1
Format
JSON over HTTPS. GET only. Times are ISO 8601, UTC.
Access
An API key from your dashboard, on an account with the Route lookup plan or a feeding receiver.
Machine-readable
OpenAPI 3.1 file

Authentication

Send your key as a bearer token on every request. The X-API-Key header works too.

Header
Authorization: Bearer ftl_live_…
  • Keys start with ftl_live_. A key is shown once, when you create it. Only a digest is stored, so a lost key cannot be recovered: revoke it and make a new one.
  • An account holds up to five keys. Use one per app or environment so you can revoke one without touching the rest.
  • Keep keys on a server. Requests from another site’s web page are refused, and a key in browser code can be read by anyone.

GET/v1/routes/{callsign}

Route lookup

Returns the origin and destination of a flight, with its airline, aircraft type and status.

Path parameter

callsignstring, required
The flight’s callsign as broadcast: the airline’s three-letter ICAO code, then the flight number. UAL1971, DAL100, FDX1234. Case does not matter. A ticket flight number such as UA1971 is not a callsign and gets invalid_callsign.

Query parameters, all optional

If you have the aircraft’s 24-bit address or its position, send them. A callsign is often flown more than once a day; these let the API pick the leg in the air now, so more lookups come back found. They are used for the match only: not stored, never returned.

hexstring
The aircraft’s 24-bit ICAO address as your receiver reports it: six hexadecimal characters, such as a1b2c3. The most reliable hint.
lat, lonnumber, together
The aircraft’s position in decimal degrees.
altinteger
The aircraft’s altitude in feet.
Request

  

Response fields

ok
true on every successful request.
callsign
The callsign you asked about, in upper case.
found
true when the flight’s route is known. When false, the fields below it are null and the request still counts.
confidence
"high": one flight fits the callsign. "medium": several legs are filed under this callsign and this is the most likely one. Send hex or the position to get high. null when not found.
airline
{ "icao", "name" } for the airline in the callsign, or null. name can be null.
origin, destination
{ "icao", "iata" }. icao is the four-character code (KORD); iata is the three-character code used on tickets and signs (ORD); a small US field without one shows its three-character US location identifier. icao can be null.
status
Where the flight is in its trip. See the values below. Can be null.
aircraftType
ICAO type designator, such as B39M or A321, or null.
updatedAt
When the flight’s record last changed, or null.

Status values

statusMeaning
scheduledA flight plan is filed. The aircraft has not moved.
taxiingMoving on the ground before takeoff.
airborneDeparted and in the air.
landedOn the ground at the destination, not yet at the gate.
arrivedThe leg is complete. A callsign flown earlier today can still answer with its finished leg until the next one is filed; check status and updatedAt, or send hex and the position.
cancelledThe flight plan was cancelled before the aircraft moved.

When nothing is found

200 OK
{
  "ok": true,
  "callsign": "UAL9999",
  "found": false,
  "confidence": null,
  "airline": { "icao": "UAL", "name": "United" },
  "origin": null,
  "destination": null,
  "status": null,
  "aircraftType": null,
  "updatedAt": null
}

GET/v1/usage

Usage

This key’s account: requests used this calendar month (UTC) and the limits that apply. Calling it costs nothing against your month; it does share your per-minute limit.

200 OK
{
  "ok": true,
  "access": "plan",
  "month": "2026-11",
  "requests": { "used": 1284, "limit": 100000, "remaining": 98716 },
  "rateLimit": { "requestsPerMinute": 60 }
}

access is plan, feeder or none.

GET/v1/status

Service status

No key needed. Use it for a health check before you page yourself.

200 OK
{ "ok": true, "status": "operational", "checkedAt": "2026-11-22T18:04:30.000Z" }

status is operational, degraded (answering, but more flights come back not found) or unavailable (HTTP 503).

Errors

Errors are JSON: { "ok": false, "code": "…", "error": "…" }. code is stable and safe to branch on. error is a sentence for people and can change.

StatusCodeMeaning
400invalid_callsignNot an airline callsign: three letters, then the flight number.
400invalid_requestAn unknown, repeated or malformed query parameter.
401unauthorizedThe key is missing, wrong or revoked.
403no_active_planThe key is valid but its account has no plan and no feeding receiver.
403cross_siteThe request came from another site’s web page.
404not_foundNo such endpoint.
405method_not_allowedOnly GET is served.
429rate_limitedOver the per-minute limit. Wait Retry-After seconds.
429quota_exceededThe month’s requests are used up. Retry-After is the time to the first of next month, UTC.
503unavailableThe service is not answering. Retry after Retry-After seconds. Not counted.

Retry a 429 or 503 after the wait in Retry-After. Anything else means the request needs fixing; sending it again gives the same answer.

Limits

Per minute
60 requests a minute per account, across all its keys.
At once
Keep to about five requests in flight at a time. A larger burst can get 503 unavailable for some of them; those are not counted, and work when sent again after Retry-After.
Per month
100,000 requests per calendar month, UTC. The count resets on the first.
What counts
Every route lookup that returns 200, found or not. Errors, /v1/usage and /v1/status are free.

Headers on every route answer

X-RateLimit-Limit
Requests a minute allowed.
X-Quota-Limit
Requests a month allowed.
X-Quota-Remaining
Requests left this month.
Retry-After
On 429 and 503: seconds to wait.

A route changes rarely during a flight. Ask once when you first see an aircraft and again when it lands or its callsign changes; polling the same callsign every few seconds only spends your month.

Coverage and privacy

  • Where. Flights in United States airspace: departing from, arriving at or crossing the United States. A flight that never enters it comes back found: false.
  • Which flights. Scheduled airline and cargo flights. Private, charter, military and blocked aircraft are never returned, under any callsign.
  • What is left out. Transponder addresses, registrations and positions are not part of any answer.
  • What we keep. A count of your requests per minute and per month, and the day a key was last used. Callsigns you look up and positions you send are not stored.

Changelog

2026-11-22
Version 1 opens with route lookup by callsign, usage and service status.

Version 1 only grows: new fields and new endpoints can appear at any time, so ignore fields you do not know. Removing or renaming a field means a version 2, and version 1 keeps running for at least six months after that.

Terms of use

By creating a key you agree to these terms.

  • Information only. The data is for information and display. It is not for navigation, flight planning, air traffic services or any other operational or safety use.
  • Your product, not a feed. You may use answers inside your own app, display or service, including a commercial one. You may not resell, sublicense or republish the data as a dataset or an API of its own.
  • Keys are yours alone. Do not share a key or publish it. You are responsible for requests made with your keys. Revoke a key at once if it leaks.
  • Fair use. Stay within the limits. Do not try to get around them with extra accounts, and do not probe for aircraft the API does not return.
  • Billing. Route lookup is $19 a month, charged in advance through Stripe. Cancel any time in your dashboard; access runs to the end of the period already paid. Payments are not refunded for a period that has started.
  • Feeders. Free access lasts while your receiver is feeding. Send only what your own receiver hears. We may remove a receiver that sends bad data.
  • No warranty. The API is provided as is. Routes can be missing, late or wrong, and the service can be unavailable. FlightTrackerLED is not liable for loss arising from its use.
  • Changes. We may change these terms, the limits or the price with notice to your account email. We may suspend a key that breaks these terms.
  • Privacy. Your account holds your email address, your keys as digests, your receivers and your request counts. See the privacy page. Questions: [email protected].