Track a shipment with its full AWB
Start with the full 11-digit air waybill number. You can enter it with or without the standard hyphen, and Panvaya resolves both forms to one canonical AWB. Keep the three-digit airline prefix and the following eight-digit serial number together: a serial number on its own is not enough to identify the shipment reliably.
The AWB prefix helps Panvaya select a supported airline tracking source. In the web form, you can let the system identify the airline or choose one when that option is available. If you choose an airline yourself, it must match the prefix on the AWB. This avoids searching the wrong carrier system and gives you a clear starting point for the shipment timeline.
One AWB, one shipment identity
Formatted and compact versions of the same full AWB resolve to the same shipment. Include the prefix and preserve leading zeros when you copy it from a document or another system.
Read the route as a sequence of flight segments
An air shipment often travels on more than one flight. A connection can change the aircraft and add an intermediate airport, while the shipment itself keeps the same AWB. Panvaya presents the route as segments so you can follow the movement between airports instead of treating the journey as one unexplained origin-to-destination line.
The shipment detail view brings the available flight legs, route points and milestones together. Depending on the information supplied by the tracking source, you can see airport codes and names, flight details, planned and actual movement times, shipment status, pieces and weight. A route map gives the itinerary a geographic context, while the event list shows the order in which recorded handling and flight milestones occurred.
Carrier data varies. A source may provide a flight number for one segment and omit it for another; it may report a planned time before an actual time is available. Panvaya shows the available fields and preserves missing values instead of presenting an estimate as a confirmed event. Times can be displayed in the relevant airport's local time, with UTC available for consistent event ordering where the airport timezone is known.
Use the Air view for day-to-day follow-up
The dashboard and shipment history let you switch between Air and Ocean tracking. Choose Air to add an AWB and open the air shipment view. The air shipment list keeps the same familiar workflow as shipment history, with filters for AWB, airline, date and status, plus export for sharing or operational review.
Open an individual shipment when you need the route and milestone detail. The page groups the current shipment summary, flight segments, route information and events in one place. That makes it easier for an operations team to answer practical questions: has the freight departed, where is its connection, did it arrive at the destination airport, and what did the carrier report most recently? The available answer depends on the source data for that AWB.
- Enter a complete AWB in the Air tracking form. Compact and hyphenated formats are accepted.
- Review the recognised airline and the shipment summary, then open the route and event timeline.
- Use the Air shipment history filters to find shipments by AWB, airline, date or status.
- Export the list when you need to share a working snapshot with colleagues.
Connect tracking to your systems
Teams can use the web interface for individual follow-up, call the developer API from their own tools, and use webhook integrations to route shipment updates into an operational workflow. The Air API accepts a full AWB and returns an air-specific response with airline identity, airport details, flight legs, milestones and route information. It uses air cargo fields rather than container, vessel or shipping-line fields, so downstream systems can handle each mode using the data that belongs to it.
The API accepts compact or formatted AWBs as the same identity. Airline selection is optional when Panvaya can detect the carrier from the prefix. A successful response can include the canonical AWB, shipment status, airport-local event times and UTC event ordering information. If a carrier does not return a field, the response leaves it unavailable rather than filling it with an assumption.
API access follows the organization's API product settings and credit balance. Air Tracking uses the shared API credit pool and distinct tracking allowance. Each successful API call consumes the configured Air credit cost. The first successful request for an AWB in a billing cycle enrolls that AWB against the distinct tracking allowance; later successful requests for the same enrolled AWB use credits but do not take another distinct tracking unit during that cycle. Failed requests are not billed, while a successful cached response is still a successful API call for credit metering.
How Air and Ocean billing works
For tracking in the web app, Air and Ocean use the same organization-level tracking allowance. A new Air shipment uses one tracking unit when Panvaya receives a successful result and saves the shipment to the account. Adding the same AWB again or refreshing an already enrolled shipment does not enroll another distinct shipment. A carrier lookup that returns no shipment or fails does not consume a new web tracking unit. Guest tracking follows its public daily allowance and does not create a saved, quota-enrolled shipment in the account.
The allowance depends on the organization's plan and configured limits. Free access includes a small monthly tracking allowance, while paid web access can add more trackings through the pricing page. Air does not introduce a second web quota to manage: the same balance covers eligible Air and Ocean shipments. Your usage view shows the organization's consumption so the team can see how much has been used and what remains.
API billing is a separate usage path. API calls draw from API credits and the API distinct tracking allowance, which Air shares with Ocean. Repeated successful requests for an AWB can incur the configured call credits, but the AWB is counted only once against the distinct shipment allowance for that billing cycle. Web tracking and API enrollment remain separate, so tracking a shipment in the dashboard does not enroll it for API billing, and vice versa.
Two ways to track, with clear usage meters
The web app uses a shared Air and Ocean tracking allowance. The API uses its credit pool and shared distinct tracking allowance. Check the usage page for the current balances and billing cycle details on your organization.
A growing airline network
Panvaya is launching Air Tracking with support for more than 25 airlines, and the supported network continues to grow. Carrier coverage depends on whether the source provides usable shipment data for a given AWB. A supported airline can still return no result for an invalid number, a shipment outside its reporting window, or a record that is not yet available in its system.
If you need an airline that is not currently available, contact Panvaya through chat support and share the airline and the AWB format you need to track. The team can review the request and, when the carrier's tracker and access are available, integrate the airline within 24 hours. This gives your team a direct way to flag a carrier gap instead of waiting for a general product update.
Supported air carriers
Panvaya supports more than 25 airlines and air cargo carriers at launch. Enter an air waybill issued under any of the following airlines to track flight legs, airport transfers and cargo status:
- Aerolíneas Argentinas
- AirAsia
- AirAsia X
- Air Caraïbes
- Air Senegal
- Akasa Air
- Azul Brazilian Airlines
- Cebu Pacific
- CMA CGM Air Cargo
- Croatia Airlines
- French Bee
- Galistair
- Hawaiian Airlines
- IndiGo Airlines
- Indonesia AirAsia
- MasAir
- Norwegian Air Shuttle
- Oman Air
- Philippines AirAsia
- Stabo Air Limited
- TAAG Angola Airlines
- Thai AirAsia
- Thai AirAsia X
- US-Bangla Airlines
- VietJet Air
- Vistara
Carrier disclaimer
All airline names, brand marks and registered trademarks referenced on this page are the property of their respective holders. Panvaya is an independent shipment tracking platform with no direct integration, formal affiliation, commercial partnership, sponsorship or endorsement from any of these carriers.
The bottom line
Air cargo moves through connected flights, airports and handling events, and visibility is most useful when those pieces appear together. Panvaya lets you track a full AWB in the web app, inspect segments and milestones, and connect air shipment data through the API and webhook workflows. Air and Ocean share the web tracking allowance, while API use follows the shared credit and distinct tracking meters. As airline coverage expands, you can request a needed carrier through chat support, with eligible integrations targeted within 24 hours.