Webhooks
Webhooks let Quiver notify your system the moment something happens, instead of you polling our API for changes. This is the recommended way to track deliveries.
Subscribing to a topic
Log into app.quiver.co.uk and go to Settings → Integrations. Add an endpoint URL for each topic you want to receive.
If you don't see a webhooks section, your integration type doesn't support them yet — contact growth@quiver.co.uk.
Available topics
| Topic | Fires when |
|---|---|
/delivery/create |
A delivery is booked |
/delivery/status-updates |
A delivery's status changes |
/inventory/updates |
Quiver-held stock levels change |
/inventory-transfer/updates |
An inventory transfer is created or updated |
Responding to events
Always respond with 200. We use the status code to confirm the event reached you. Any other code — or a timeout — means we treat the event as undelivered.
Practical guidance:
- Respond quickly. Acknowledge with
200first, then do your processing in the background. Slow handlers risk timing out. - Be idempotent. Handle receiving the same event more than once without double-processing — match on
taskIdand ignore anything you've already applied. - Don't assume ordering. Status events may arrive out of sequence. Treat each as "current state" and ignore any older than what you already hold.
- Reconcile if in doubt. If your endpoint was down, query the API directly (for example by
merchantOrderId) rather than waiting for a replay.
