API docs
Sous Chef Ordering API
Request access

Webhooks

Sous Chef sends what happens to your orders, and to the items your stores sell, to one url registered for your channel. To register or change the url, contact support@yoursouschef.com. It cannot be changed through the API.

Events

EventWhenReference section
order.status.updatedThe order became ready, or finished.Orders
order.rejectedThe order was rejected at intake: the store was paused or closed.Orders
order.cancelledThe order was cancelled, by the restaurant or by you.Orders
order.delivery.updatedThe order's delivery status changed.Orders
item.availability.changedAn item or modifier option became unavailable, or available again.Menus

You receive order events for the orders that you sent, and item events for the stores on your channel. An order that is not rejected is in the kitchen, and fetchOrder confirms its status at any time.

A page for an event in the API Reference documents its payload. It is not a separate endpoint.

Envelope

Every delivery is an HTTPS POST with a JSON body:

{
  "id": "8c1d…",
  "event": "order.status.updated",
  "timestamp": "2026-11-18T18:04:11.123Z",
  "organization_id": "<your organization id>",
  "data": {}
}
  • id is the unique event id and your deduplication key. Deliveries are unordered and can repeat: you will receive some events more than once, and every copy carries the same id.
  • event is the event type.
  • timestamp is when this delivery was sent, not when the event happened.
  • organization_id is your channel's organization id. It is the same on every delivery to you, and it is not the restaurant's id.

Acknowledging a delivery

Return any 2xx within 30 seconds to acknowledge a delivery. Acknowledge first and process asynchronously. Your url must be https on a public address. A redirect is not followed and counts as a failure.

Retries

Any other answer, or no answer, is a failed attempt. Each delivery is attempted up to five times, with a growing pause of 5 to 40 seconds between attempts. Webhooks keep you current without polling, and they are not the only record: fetchOrder returns the current state of any order you sent, so reconcile from it after an outage on your side.

Signatures

Every delivery is signed. The signature is in the X-SousChef-Signature header: a JWT signed with our private key, which you verify with a public key that you fetch from us. Verify the signature before you act on a delivery. See Verifying webhook signatures.

Every delivery also carries the same values under X-OneTablet-Signature and X-OneTablet-Timestamp, for backward compatibility.