Webhooks
Sous Chef pushes what happens to your orders and stores to one url registered for your channel. It is set by support@yoursouschef.com, which also changes it on request; no operation on this API changes it.
Events
| Event | When | Reference section |
|---|---|---|
order.created | The restaurant received your order. Not sent yet, coming before sandbox access. | Orders |
order.status.updated | The order moved through its lifecycle (accepted, ready, finished). | Orders |
order.rejected | The order was rejected, by the restaurant or automatically at intake. | Orders |
order.cancelled | The order was cancelled, by the restaurant or by you. | Orders |
order.delivery.updated | The order's courier status changed. | Orders |
store.status.changed | A store on your channel was paused, resumed or observed offline. Not sent yet, coming before sandbox access. | Stores |
item.availability.changed | An item was 86'd or restocked at a kitchen behind a store on your channel. | Menus |
You receive order events for the orders you sent, and store and item events for the stores on your channel. A page per event in the API Reference is documentation of its payload, not a separate endpoint.
Envelope
Every delivery is an HTTPS POST with a JSON body:
{
"id": "8c1dā¦",
"event": "order.created",
"timestamp": "2026-11-18T18:04:11.123Z",
"organization_id": "<your organization id>",
"data": {}
}
idis the unique event id and your deduplication key. Deliveries are at-least-once and unordered: you will receive some events twice, and every copy carries the sameid.eventis the discriminator, also sent as theX-Event-Typeheader.timestampis when this delivery was sent, not when the event happened.organization_idis your channel's organization id ā the same on every delivery to you ā not the restaurant's.
Return any 2xx to acknowledge. Anything else, or no answer, is retried with exponential backoff.
Signatures
Every delivery is signed with the v2 scheme, in the X-OneTablet-Signature header: a JWT signed with our private key and verified with a public key you fetch from us. Verify it before you act on a delivery. The algorithm, the claims and the key endpoint are the same as on the Management API; see Concepts ā Verifying webhook signatures.