Subscribe to tracking events for a parcel

This endpoint allows a user to subscribe to tracking events via webhooks for a specific parcel, identified by its Sendle reference (ref). Once subscribed, the user will receive real-time tracking updates via webhooks to the callback endpoint url on the account.

The initial response to this subscription request will include all existing tracking events associated with the parcel. Webhook events are only sent for updates that occur after the subscription is created.

Note: A webhook endpoint must be registered on the account before a subscription can be created. You can add a callback endpoint url through the account dashboard under Settings --> API.

Here's most of our tracking events and what they mean:

Tracking EventDescription
Pickup AttemptedDriver attempted to pickup the parcel.
PickupParcel successfully picked up.
Drop OffParcel has not yet been dropped off.
Dropped OffParcel left at a drop-off location.
InfoInformation about the parcel. This can come from us or the delivery partner.
In TransitParcel in transit between hub locations.
Out for DeliveryDriver has the parcel and is taking it to be delivered.
Delivery AttemptedParcel delivery attempted, but unsuccessful.
DeliveredParcel successfully delivered.
Local DeliveryDelivery is being handled by a local partner (e.g. a local postal service or similar).
Card LeftParcel delivery attempted and a card has been left for the receiver to arrange collection or re-delivery.
Left with AgentParcel has been left with a parcel connect location, POPStation, or similar for collection.
DamagedParcel has been marked as damaged.
Unable to DeliverParcel could not be delivered.
ExpiredThe label for this parcel has expired.

If you receive an event type not on this list, look at the description of the event for more information.

Path Params
string
required

The order's unique reference. This is the short ID that can be shared, for example SNFJJ3 or S34WER4S.

This isn't the internal order ID that's used for other API calls.

Headers
string

Name of your service, site, or some other informative value.

Including this lets our team identify your requests and ensures that they aren't blocked by our security tools.

Responses

500

Indicates that an unhandled error has occured with the Sendle API. We may have more information on the Sendle Status page. Contact [email protected] if the problem persists.

Language
Credentials
Basic
base64
:
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
*/*