This endpoint facilitates retrieving tracking events linked to your booking but is not needed if we automatically activate the booking callback which is the preferred solution as it brings all booking updates and tracking events via the same API.

To pull the latest tracking of any air waybill, call this endpoint with the awb query parameter. To get the tracking linked to a booking made through the API, use flight-uuid.

202 Accepted: tracking still in progress

When an airline is slow to send tracking data and there is no result within about 20 seconds, the call returns 202 Accepted instead of making you wait.

{
  "message": "Your tracking request is in progress and is taking longer than usual. Please retry the same AWB in one to two minutes; the result will be served from our cache."
}

What it means: a 202 is not an error. The AWB is not invalid or unknown: the data is still being fetched from the airline.

What to do: call again with the same AWB (and the same flight-uuid, if you sent one) up to 2 minutes later. The result is usually in our cache by then and comes back fast with 200 OK and the full tracking events.

Recommended retry logic:

• Wait 30 to 60 seconds after a 202, and keep retrying for up to 2 minutes.
• Do not retry in a tight loop: it does not make the airline answer faster.
• Still 202 after about 2 minutes: try again later, or subscribe to tracking updates to get the result pushed to you.

Billing: a 202 uses no credits. Only the call that returns the tracking data (200) is charged.