One API can track air cargo on many airlines because every air waybill starts with a 3 digit airline prefix that tells the system which airline to ask. An air cargo tracking API reads the prefix, matches it to the issuing airline, retrieves that airline's events, and returns them in one format. How far this works depends on carrier coverage: which airlines the provider connects to, and how much data each one shares.
This guide explains how prefixes identify airlines, how coverage works, how an AWB number is processed, how interline shipments are tracked, and how to evaluate a provider before you integrate.
What Is a Multi-Airline Tracking API?
It is an interface that lets one integration retrieve shipment events from many airlines. You send an AWB number to one provider, and the provider deals with the carriers behind it. That is the idea of multi-airline cargo tracking: one request format, one response format, many airlines. Providers also describe the service as multi-carrier air cargo tracking.
The alternative is a separate airline tracking integration for every carrier, each with its own login, data format, and update pattern. Airline tracking data also differs from one carrier to the next. An airline tracking API provides a unified way to retrieve shipment events without building a separate integration for every carrier. Some airlines publish detailed events and others very little, so a single interface hides the connections but not the differences in what the airlines share. A multi-airline tracking API gives businesses one consistent way to retrieve shipment events across supported carriers. A single airline tracking API also standardizes access to tracking data, regardless of which carrier handles the shipment.
How AWB Prefixes Identify Airlines
AWB airline identification starts with the first three digits of the number. Everything after them identifies the shipment.
Understanding the Three-Digit Airline Code
An AWB number has eleven digits: a three-digit prefix, a seven-digit serial number, and a check digit. The prefix is assigned to an airline, so one prefix points to one airline. The air waybill prefix identifies the issuing carrier before the tracking request is processed. The airline AWB prefix also allows the tracking system to identify which carrier should receive the request. An airline can hold more than one, though: Vizion's published carrier table lists United under 016, 107, and 215. In a tracker, the airline AWB prefix is the routing key. Without it, the system has nothing to route the search by, and this is the first detail a tracker checks.
Numeric Airline Codes vs IATA and ICAO Codes
Airlines carry three different codes, and they are easy to confuse:
IATA airline code: two characters, such as AA, used in reservations, timetables, and other commercial documents.
ICAO airline code: three letters, such as AAL, used in aviation operations and call signs.
The numeric prefix: three digits at the start of the waybill, which IATA calls an accounting or prefix code.
The three systems are separate, and no formula converts one into another. That is why providers keep an AWB prefix lookup table that maps each prefix to an airline name and its other codes.
How APIs Identify the Issuing Airline
The API takes the first three digits, finds the prefix in its table, and identifies the issuing airline. ShipsGo notes that its system identifies the airline automatically, so you do not select it. Vizion's documentation says master numbers are routed by prefix, with no carrier code needed.
This works for a MAWB, the master air waybill issued by the airline. A HAWB is issued by a forwarder, so it carries no airline to look up. Vizion's documentation, for example, asks for a forwarder code or a linked master number when you track one.
How Carrier Coverage Works in Air Cargo Tracking APIs
Air cargo API carrier coverage means the set of airlines a provider can retrieve data from. It is not one number to compare. Airline carrier coverage differs in three ways: which airlines are included, which events each one provides, and how often the data is refreshed. Vizion's documentation shows the level of detail to look for: it lists airlines in a table and notes, for instance, that customs data is not available for three of them. An air cargo tracking API should make these differences clear before a business commits to an integration.
Supported Airlines vs Available Tracking Data
A listed airline is one the provider can query. That does not guarantee data for every shipment. Airline tracking availability also changes over time, and a listed airline may show nothing for a new booking until the first event is recorded. Check two things separately: whether the airline is listed, and which events it provides.
How to Check Airline Coverage Through an API
Look in the documentation for an endpoint that returns the list. Qubictron's documentation includes a reference for the endpoint that lists its airlines. Search for a supported airlines tracking API endpoint in any provider's docs, or ask the vendor for the list. A good airline coverage API lets you run an airline coverage check before you integrate and again whenever a customer ships with a new carrier. If the list includes a carrier support status for each airline, use it to separate carriers that are fully connected from those that are limited.
Active Airlines, Maintenance and Temporary Data Gaps
An airline on the list can still have gaps. Its system may be under maintenance, or the provider's connection to it may be down for a while. Shipments on that airline can then show no new events until the connection returns. Treat the gap as temporary, keep the last known events, and check again later.
How a Multi-Airline Tracking API Processes an AWB Number
Behind one request, the API normally runs four steps.
Step 1. Validate the AWB Number and Prefix
The API checks that the number has eleven digits, that the check digit fits, and that the airline AWB prefix exists. Validating the air waybill prefix helps ensure that the request is routed using the correct airline information. Qubictron's Air Tracking endpoint expects the number as XXX-XXXXXXXX, and its documentation lists response statuses such as WRONG_REFERENCE_NUMBER for numbers that fail.
Step 2. Match the Prefix to a Supported Airline
The prefix is looked up in the airline table, and the lookup is only as complete as that table. A reliable AWB prefix lookup should also identify the issuing airline from the three-digit number. If it matches an airline the provider supports, the request continues. If not, the API cannot say where to ask, and the number is reported as not recognized or unsupported.
Step 3. Retrieve Available Shipment Events
The API asks the airline's source for whatever it publishes. The result may include shipment milestones such as booked, received, departed, arrived, and delivered, depending on the airline. Flight status is a separate data set: it shows where the aircraft is, not the cargo.
Step 4. Return Tracking Data in a Standardized Format
Each airline has its own codes and wording, so the API maps them to a common set of milestones and returns structured data, typically with an event code, a timestamp, a location, and a flight number. Vizion's sample response, for instance, shows a UTC timestamp and a flight number on each flight event.
Tracking Interline Shipments Across Multiple Airlines
Interline cargo travels on two or more carriers under one air waybill. Tracking it is harder because the airlines involved may not report in the same way.
Issuing Airline vs Operating Airline
The prefix identifies the issuing airline, which is the airline named on the waybill. The operating airline is the one flying a particular leg. On a direct flight they are often the same, but on an interline shipment they are not, so the prefix alone does not tell you who is carrying the cargo now.
Why One AWB Can Include Multiple Flight Carriers
No single airline serves every route. A shipment may fly the first leg on the issuing airline and the next on a partner, with a handover in between. Status codes such as TFD, transferred, and RCT, received from another airline, record that step. Flight numbers in the event list show which airline operated each leg.
Limitations of Interline Cargo Tracking
The API shows what its sources report. If the issuing airline's system does not receive events from the partner, the history can stop at the handover while the cargo keeps moving. Details also vary between airlines, so the same milestone may be described differently on two legs. Treat a pause after a transfer as a possible reporting gap, not proof of a delay.
Common Airline Coverage and AWB Tracking Problems
AWB Number Not Recognized
Typical causes are a typo, a missing prefix, a house number, or an airline the provider does not support. Check the three digits against the published prefix list, then confirm the airline is on the coverage list.
Airline Supported but Shipment Not Found
The airline may not have recorded a first event yet, the number may belong to a different shipment than you expect, or the airline may publish little data. Wait for the first handling event, then confirm that you are searching with the master number.
Airline API Temporarily Unavailable
When the provider cannot reach an airline, new events wait until the connection returns. Retry later, and avoid reading a missing update as a stopped shipment.
Missing Events from Connecting Airlines
Events from a partner airline may not reach the issuing airline's records. Check the flight numbers of the later legs and, if needed, ask your forwarder or the airline's cargo desk.
How to Evaluate Airline Coverage Before Choosing a Tracking API
Test with your own shipments instead of relying on a list of logos. Air cargo API carrier coverage looks similar on every marketing page, and airline carrier coverage only becomes clear when you run real numbers:
Collect AWB numbers from your main airlines, including one interline shipment, one delivered shipment, and one invalid number.
Check that each airline is on the provider's list and that its events match the airline's own site.
Compare milestones and timestamps for consistency across airlines.
See how the API reports gaps, airlines it does not support, and errors.
Ask how quickly new events appear and how outages are handled.
You can try the same numbers without code in Qubictron's air tracking before deciding on an integration.
Frequently Asked Questions
Can an API Identify the Airline from an AWB Number?
Yes. The first three digits point to the issuing airline, and the API looks them up in its table.
Does Every Airline Have a Unique AWB Prefix?
Each prefix belongs to one airline, but an airline can hold several prefixes.
Can One Tracking API Support Multiple Airlines?
Yes. That is the purpose of a multi-airline design, but coverage depends on the provider, so check your carriers.
Does the AWB Prefix Identify the Operating Airline?
No. It identifies the issuing airline. The operating airline for each leg appears in the flight data.
Why Is an AWB Not Found Even When the Airline Is Supported?
The first event may not be recorded yet, the number may be wrong, or the airline may publish little data. Check the number and wait for the first event.
Building Reliable Multi-Airline Cargo Tracking
Reliable tracking starts with the prefix, continues with honest coverage information, and ends with clear handling of gaps. Choose a provider whose airline list you can check, test it on your own AWB numbers, and treat each missing event as a question to answer rather than a failure to hide.