Parameters
| Query parameter | Meaning | Example |
|---|---|---|
bookingReference | Booking reference (the HBL number). Nine alphanumeric characters. | AIRLCHN133184 |
equipmentReference | Container number in the BIC ISO format, up to 15 characters. | CMAU1234567 |
Send Authorization: Bearer <token> with every request. The token comes from the OAuth 2.0 client credentials flow and must carry the trackntrace:read scope.
Example request
curl 'https://api.airliftusa.com/api/v1/api-service/external/trackntrace?bookingReference=AIRLCHN133184' \
--header 'Authorization: Bearer YOUR_TOKEN'Example response (200)
{
"success": true,
"statusCode": 200,
"data": [
{
"eventID": "lMZQf2mGf4q4jF8m2QG7F8C5iY7sH9TgJ0l5vH8tZ8c",
"eventType": "EQUIPMENT",
"eventClassifierCode": "ACT",
"eventDateTime": "2019-11-10T07:41:00+08:00",
"eventCreatedDateTime": "2021-01-07T14:12:56Z",
"equipmentReference": "CMAU1234567",
"ISOEquipmentCode": "22G1",
"transportEventTypeCode": "GATI",
"eventLocation": { "UNLocationCode": "USNYC", "locationName": "Port of New York" },
"transportCall": {
"UNLocationCode": "USNYC",
"facilityTypeCode": "POTE",
"modeOfTransport": "VESSEL",
"carrierServiceCode": "AS1",
"exportVoyageNumber": "123A",
"vessel": { "vesselIMONumber": "9876543", "vesselName": "Demo Vessel" }
}
},
{
"eventID": "j5A5tC2a1W5W4YV4K9O2k2Ih9J7GfC0l3H1bP2oB4KQ",
"eventType": "TRANSPORT",
"eventClassifierCode": "ACT",
"eventDateTime": "2019-11-12T07:41:00+08:00",
"transportEventTypeCode": "DEPA",
"eventLocation": { "UNLocationCode": "USNYC", "locationName": "Port of New York" }
}
],
"metadata": { "timestamp": "2025-06-19T11:00:11Z" }
}- eventType is SHIPMENT, EQUIPMENT or TRANSPORT; eventClassifierCode is ACT for an actual event, PLN for a planned one and EST for an estimate.
- Equipment events carry equipmentReference (the container) and ISOEquipmentCode; transport events carry the transportCall with the vessel, voyage and UN/LOCODE.
- eventDateTime is when the event happened at the location, with its local offset; eventCreatedDateTime is when it reached the Airlift system.
Other status codes: 400 missing or invalid parameter, 401 token missing or expired, 403 scope not granted, 404 nothing matches the reference, 500 server error. Limits are 60 requests a minute and 4,000 an hour per consumer, reported in the X-RateLimit-* headers.
Frequently asked questions
Which identifiers can I track by?
The booking reference (Airlift house bill number) or the container number. Send at least one; sending both narrows the result to that container on that booking.
Is this the DCSA Track and Trace format?
Yes. The product is published as DCSA 3.0.0 compliant and the event shape follows the DCSA Track and Trace interface, so the same consumer can read Airlift events and events from DCSA-aligned carriers.
Does it cover rail and trucking after discharge?
Yes. Inland and rail transport legs that belong to the booking are returned as events alongside the ocean legs.
Other endpoints
- GET /booking · Ocean Booking
- POST /bookings · Ocean Booking Service
- GET /documents · Commercial Shipping Documents
- GET /invoices · Invoices Data Service
- GET /invoice · Invoice Data
- All API documentation
- Free tariff API
Need access? Register your application in the developer portal; the API is open to approved Airlift customers.