Shipment Status Webhooks
Instead of polling for shipment status, register an HTTPS endpoint and receive a signed webhook for every milestone: picked up, in transit, out for delivery, delivered, and exception. Deliveries are signed with an HMAC signature header so receivers can verify authenticity, and failed deliveries retry with exponential backoff for 24 hours.
- Service type
- Outbound Webhook
Events
shipment.picked_up
shipment.in_transit
shipment.out_for_delivery
shipment.delivered
shipment.exception
Inline message schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"title": "ShipmentEvent",
"type": "object",
"required": [
"event",
"shipment_id",
"occurred_at"
],
"properties": {
"event": {
"type": "string",
"description": "Milestone name, e.g. shipment.delivered."
},
"shipment_id": {
"type": "string"
},
"order_id": {
"type": "string"
},
"occurred_at": {
"type": "string",
"format": "date-time"
},
"location": {
"type": "string",
"description": "Last scanned facility or city."
},
"carrier": {
"type": "string"
},
"detail": {
"type": "string",
"description": "Human-readable status detail."
}
}
}
Sample payload
Example message — placeholder values
{
"event": "string",
"shipment_id": "string",
"order_id": "string",
"occurred_at": "2026-01-01T00:00:00Z",
"location": "string",
"carrier": "string",
"detail": "string"
}
Register your endpoint with the logistics team. Verify the HMAC signature on every request before processing. Respond 2xx within 10 seconds; anything else counts as a failed delivery and is retried. The payload schema is shown on the Messages tab.
- Payload security
- HMAC signature
- Retry policy
- Exponential backoff: 1m, 5m, 30m, 2h, then hourly up to 24h; dead-lettered after final failure.
No specification files are attached to this integration.