BPost Track & Trace
The action is used to get the tracking information from BPost.
Inputs
| Name | Type | Description |
|---|---|---|
| Tracking Number | String | Bpost tracking number |
Outputs
| Name | Type | Description |
|---|---|---|
| Found Tracking? | Boolean | Whether the tracking information was found True / False |
| Status | String | Tracking status: Ready for Shipment, Delivered, In Transit, Problem with Delivery, Returning to Sender, Ready for Pickup |
| Status Description | String | Detailed description of the tracking status |
| Shipped Date | String | The date of the shipment. Format: YYYY-MM-DDThh:mm:ss |
| Last Event Date | String | The date of the last tracking event. Format: YYYY-MM-DDThh:mm:ss |
| Tracking URL | String | Tracking URL |
| Activity History | List | List of all the tracking events. See the example below |
Sample Response
Activity History
Tracking Status
BPost API returns a status code for each tracking event. DG maps this status code to one of the predefined statuses. E.g. pre-tansit - Ready for Shipment.
Because the status code doesn't describe all the tracking statuses, DG uses the event description and maps it to one of the predefined statuses. E.g. returned to shipper - Returning to Sender.
Statuses mapping
Status descriptions treated as Returning to Sender:
*return to sender
returned to shipper
returned to sender
Updated 4 months ago