Order delivery updated
Courier lifecycle of an order. Deduplicate on the envelope's id: successive courier transitions of one order are separate events with separate ids.
Request
- idstring
Unique event id — the deduplication key.
Deliveries are at-least-once and unordered, so you WILL receive the same event more than once. Every copy of one event carries the same
id. Two legitimate transitions of the same order or store are two different events and carry two different ids.Key your idempotency on this field alone.
timestampis the moment the attempt was SENT and differs between copies of one event. - eventstring
Always
order.delivery.updated.Possible values: [order.delivery.updated] - timestampstring<date-time>
When this delivery was SENT — not when the event happened. Order by the transported state, never by arrival.
- organization_idstring
Your channel's organization id — the same on every delivery to you — also carried on the delivery's
X-Organization-IDheader. It is your channel's organization, not the restaurant's.Snake case on this ONE field is a long-lived wire value shared with the Management API; every other field on this API is camelCase.
Treat it as a sanity check, never as proof of origin. Proof of origin is the
X-OneTablet-Signatureheader, which every delivery on this API carries; see "Verifying webhook signatures". - dataOrder
The order, carrying its new
deliveryStatus.
{
"id": "00000000-0000-0000-0000-000000000000",
"event": "order.delivery.updated",
"timestamp": "2026-01-01T00:00:00Z",
"organization_id": "00000000-0000-0000-0000-000000000000",
"data": {
"id": "00000000-0000-0000-0000-000000000000",
"platformOrderId": "00000000-0000-0000-0000-000000000000",
"status": "new",
"deliveryStatus": "ASSIGNED",
"createdAt": "2026-01-01T00:00:00Z",
"updatedAt": "2026-01-01T00:00:00Z",
"estimatedReadyAt": "2026-01-01T00:00:00Z",
"rejectReason": "<rejectReason>",
"rejectReasonCode": "itemOutOfStock",
"store": {
"id": "00000000-0000-0000-0000-000000000000",
"externalId": "00000000-0000-0000-0000-000000000000",
"location": "<location>",
"brand": "<brand>",
"platform": "<platform>"
},
"cancellation": {
"by": "<by>",
"reason": "<reason>",
"reasonCode": "itemOutOfStock",
"at": "2026-01-01T00:00:00Z"
},
"details": {
"externalId": "00000000-0000-0000-0000-000000000000",
"externalReadableOrderNum": "<externalReadableOrderNum>",
"placedAt": "2026-01-01T00:00:00Z",
"estimatedPickupAt": "2026-01-01T00:00:00Z",
"isPickup": true,
"isMerchantDelivery": true,
"subtotal": 50,
"tax": 50,
"tip": 50,
"deliveryFee": 50,
"total": 50,
"items": [
{}
],
"promotions": [
{}
]
}
}
}About Orders
Send orders to the restaurants on your channel, move them along, and read them back.
Stores are addressed by their code from fetchStores. A code that is unknown, retired or not on your channel answers 404, indistinguishably. Orders are addressed by YOUR id, platformOrderId: together with storeCode it is the idempotency key. Sous Chef's own id for the order arrives as id on every order.* webhook and on fetchOrder.
200 on a write means we accepted the call for processing, not that the restaurant accepted the order: that arrives as an order.created or order.rejected webhook (order.created is not sent yet, coming before sandbox access). Every write is idempotent, so retry on 500 / 503 freely.