AWBStandardStatus¶
Returns the tracking of an AWB: a header with its current status and the list of standard statuses it went through, ordered by date.
URL¶
POST https://ocelot.servientrega.us/api/Tracking/Track/AwbStandardStatus
POST https://ocelotkiwi.azurewebsites.net/api/Tracking/Track/AwbStandardStatus
Parameters¶
| Name | Type | Required | Rules |
|---|---|---|---|
shippingId |
number | Yes | AWB number |
language |
text | Yes | EN English or ES Spanish. The statuses have the same meaning in both languages |
Request example¶
curl -X POST "https://ocelot.servientrega.us/api/Tracking/Track/AwbStandardStatus" \
-H "Authorization: Bearer <ACCESS_TOKEN>" \
-H "Content-Type: application/json" \
-d '{ "shippingId": 2290000001, "language": "EN" }'
curl -X POST "https://ocelotkiwi.azurewebsites.net/api/Tracking/Track/AwbStandardStatus" \
-H "Authorization: Bearer <ACCESS_TOKEN>" \
-H "Content-Type: application/json" \
-d '{ "shippingId": 2290000001, "language": "EN" }'
awbImage no longer contains the image
Since November 2026, awbImage does not contain the delivery image in base64. When the AWB has a
delivery image, the field contains a text with the path to download it; when it does not, the field is
null. The field is kept so existing integrations do not break.
To know whether the image exists, read hasDeliveryProof. To download it, use
Delivery proof image with the same token.
Response example¶
{
"result": true,
"entities": [
{
"header": {
"shippingId": 2290000001,
"reference": "ORDER-10001",
"awbDate": "2026-05-04T13:43:28.16Z",
"destinationCountry": "COLOMBIA",
"destinationCity": "BARRANQUILLA",
"currentStatus": "DELIVERED",
"awbImage": "Se obtiene en /api/DestinationStatus/track/DeliveryProof?awb=2290000001. Por favor refiérase a la documentación.",
"estimatedDeliveryDate": "2026-05-07T18:07:35Z",
"hasDeliveryProof": true
},
"details": [
{
"shippingId": 2290000001,
"idStatus": 1,
"status": "CREATED ORDER",
"dateTrack": "2026-05-04T13:43:28.16",
"location": "MIAMI",
"detail": "Create AWB"
},
{
"shippingId": 2290000001,
"idStatus": 3,
"status": "SEND TO INTERNATIONAL DEPARTURE",
"dateTrack": "2026-05-05T18:15:00",
"location": "MIAMI",
"detail": "729-00000000"
},
{
"shippingId": 2290000001,
"idStatus": 13,
"status": "DELIVERED",
"dateTrack": "2026-05-07T18:07:35",
"location": "BARRANQUILLA",
"detail": "ENTREGADO"
}
]
}
],
"messages": [
"Tracking returned sucessfully. Dates returned in UTC."
],
"notificationType": 3
}
header¶
| Field | Meaning |
|---|---|
shippingId |
AWB number |
reference |
The reference sent when the AWB was created |
awbDate |
Creation date of the AWB |
destinationCountry / destinationCity |
Destination |
currentStatus |
Current standard status |
awbImage |
Path to the delivery image, or null. See the warning above |
estimatedDeliveryDate |
Estimated or actual delivery date, when the destination operator reports it |
hasDeliveryProof |
true when the delivery image is available |
The response may include other fields (for example currentStep, currentState or lastOperatorQueryUtc) used by
our tracking page. Ignore the fields you do not use: new fields may be added without notice.
details¶
| Field | Meaning |
|---|---|
idStatus |
Standard status code (see the table below) |
status |
Standard status name, in the requested language |
dateTrack |
Date of the status |
location |
Place where it happened, when known |
detail |
Additional information. With status 3, the Master Air Waybill (MAWB) number |
All dates are in UTC.
Standard statuses¶
idStatus |
Stage | Status | Additional info |
|---|---|---|---|
| 1 | USA operation | CREATED ORDER | No |
| 2 | USA operation | RECEIVED IN MIAMI HUB | No |
| 3 | USA operation | SEND TO INTERNATIONAL DEPARTURE | No |
| 4 | USA operation | DELAY IN INTERNATIONAL DEPARTURE | Yes |
| 5 | USA operation | ARRIVE TO DESTINATION COUNTRY | No |
| 6 | Customs operation | STARTING CUSTOM PROCESS | No |
| 7 | Customs operation | ENDING CUSTOM PROCESS | No |
| 8 | Customs operation | CUSTOMS CLEARANCE RETENTION | Yes |
| 24 | Customs operation | CUSTOMS REVIEW | Yes |
| 9 | Last mile operation | ENTRY LAST MILE OPERATION | No |
| 10 | Last mile operation | DEPARTURE TO DESTINATION CITY | No |
| 11 | Last mile operation | ENTRY DESTINATION CITY | No |
| 12 | Last mile operation | LOCAL DISTRIBUTION | No |
| 13 | Last mile operation | DELIVERED | No |
| 14 | Last mile operation | LAST MILE DELIVERY DELAY | Yes |
| 15 | Last mile operation | RETURN TO SENDER | Yes |
| 16 | Last mile operation | LOST | Yes |
| 17 | Last mile operation | REFUNDED | Yes |
| 18 | Last mile operation | VOIDED | Yes |
| 19 | Last mile operation | ABANDONED | Yes |
| 20 | Last mile operation | OTHER | Yes |
| 21 | Last mile operation | RETURN TO MAIN HUB | Yes |
| 22 | Last mile operation | IN CLAIM PROCESS | Yes |
| 23 | Last mile operation | WAITING FOR PICKUP | Yes |
| 25 | Last mile operation | REJECTED BY CUSTOMER | Yes |
| 26 | Last mile operation | DATA CONFIRMATION PROCESS REQUIRED | Yes |
"Additional info: Yes" means the status usually needs an action or a follow-up; detail explains it.
Notes¶
- Use
idStatusin your logic, not thestatustext. - Invalid or expired token: this method answers
400withmessages: ["TURNSTILE_INVALID"]andnotificationType: 1, instead of401. When you receive it, request a new token and repeat the request.