API docs
Sous Chef Ordering API
Request access

Order rejected

Webhookorder.rejected

An order was rejected at intake, because the store was paused or outside its hours.

Request

application/json
required
  • idstring

    Unique event id: the deduplication key.

    A delivery that is not acknowledged is sent again, and deliveries are 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 are two different events and carry two different ids.

    Key your idempotency on this field alone. timestamp is the moment the attempt was SENT and differs between copies of one event.

  • eventstring

    Always order.rejected.

    Possible values: [order.rejected]
  • 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. It is your channel's organization, not the restaurant's.

    Snake case on this one field is a long-lived wire value; 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-SousChef-Signature header, which every delivery on this API carries (the same value is also sent as X-OneTablet-Signature, for backward compatibility); see "Verifying webhook signatures".

  • dataOrder

    The order, with status: rejected.

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: it is the idempotency key, and it must be unique across every order you send. 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 order has reached the kitchen. An order for a store that is paused or outside its hours comes back as an order.rejected webhook. Every other order goes to the kitchen: fetchOrder returns it, and its progress arrives as order.status.updated when it becomes ready and then finished. Every write is idempotent, so retry on 500 / 503 freely.