HMAC Authentication
Deliverect can sign outgoing webhook requests using HMAC-SHA256, allowing you to verify that requests genuinely originate from Deliverect and have not been tampered with in transit. This can be achieved using a pre-shared secret configured on your integration.
| WEBHOOK | TYPE | FUNCTION |
|---|---|---|
| Channel Registration | POST | Any channel integrator will provide a standardised registration URL to facilitate customer onboarding/offboarding. |
| Checkout Update | POST | Triggered after a customer completes checkout. Sends the final basket and checkout status to your endpoint. |
| Menu Update | POST | Customers will publish their menu to a provided webhook URL. This delivers JSON containing all the necessary attributes to display their menu as intended. |
| Snooze / Unsnooze Products | POST | When items are out of stock or temporarily unavailable, a snooze event is sent to instruct channels to make items unavailable. When items become available again, an unsnooze event is sent. |
| Busy mode | POST | When a store is paused, a webhook event is sent to ensure no further orders can be received. When re-opened, an event is sent to set the store back online. |
| Courier Update | POST | Courier-related updates are sent to provide new information about the courier journey whenever a change applies. |
| Order Status Update | POST | Whenever a POS updates the status of an order, a webhook event is sent with the updated order details. |
| Preparation Time Update | POST | A webhook is sent to indicate that a preparation time update for an order has been applied. |