/opensky/tracks

POST /api/opensky/tracks

Price: 1 credit

Get the live flight track (waypoints) for an aircraft by its ICAO 24-bit address

How to use it

Get the live flight track of an aircraft by its ICAO 24-bit transponder address (lowercase hex). Returns the callsign, track start/end timestamps, and an ordered list of waypoints; each waypoint has a timestamp, latitude, longitude, barometric altitude, true track (heading), and on-ground flag. Reflects the aircraft's current ongoing flight.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• icao24 string required — Aircraft ICAO 24-bit transponder address (lowercase hex) (examples: "3c6444"; minLength: 6; maxLength: 6)

Response

• @type string (default: "OpenskyTrack")
• icao24 string required
• callsign string nullable
• start_time integer nullable
• end_time integer nullable
• path array (default: [])
  • @type string (default: "OpenskyTrackWaypoint")
  • time integer nullable
  • latitude number nullable
  • longitude number nullable
  • baro_altitude number nullable
  • true_track number nullable
  • on_ground boolean nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No live track found for the given aircraft Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.