Webhook Events
| Event | Sent when | Default subscription |
|---|---|---|
order.processing |
The order left the queue and is being executed | optional |
order.success |
Diamonds delivered | yes |
order.failed |
Permanently failed, amount refunded | yes |
order.cancelled |
Cancelled, amount refunded | yes |
order.delayed |
Temporarily delayed, still processing | optional |
Choose the events per API key in the Client Dashboard. order.success, order.failed and order.cancelled are the final events — subscribe to at least those.
#Headers on every delivery
| Header | Example | Purpose |
|---|---|---|
X-Boostigo-Event |
order.success |
Event name (same as body event) |
X-Boostigo-Delivery |
evt_A8H72K |
Unique delivery id — use it to de-duplicate |
X-Boostigo-Timestamp |
1788794127 |
Unix time the request was signed |
X-Boostigo-Signature |
sha256=… |
HMAC-SHA256 — see Verify Signature |
User-Agent |
Boostigo-Webhooks/1.0 |
#Ordering
Events for one order are sent in lifecycle order, but network retries can reorder deliveries. Always treat the status inside data as authoritative and ignore an event whose status is "older" than what you already stored (e.g. a late order.processing after order.success).