Tracking webhooks: an integration checklist
What to confirm in the documentation before your order-status page depends on push events.
Before you build
- Signature. Does the provider sign each request, and with what? Verify the signature on every call and reject anything that fails.
- Retries. How many attempts, over what period? Can you replay missed events?
- Duplicates and order. Assume an event can arrive twice or late. Make the handler idempotent and compare event timestamps before overwriting state.
- Event types. Which statuses exist, and which should trigger a customer message?
- Raw data. Can you still see the carrier's original checkpoint text?
While you build
Respond quickly with a success code and process asynchronously; slow handlers cause retries. Log the event identifier. Keep a scheduled poll for shipments that have been silent for too long.
Where to find this
The specifics live in each provider's webhook documentation, linked from its profile. Products with documented tracking webhooks are listed under Tracking Webhook APIs.
We link to official docs, pricing and terms. Unconfirmed fields stay marked as unknown.