OrderDeliveryUpdatedEvent

Fields

• eventstring

  Always order.delivery.updated.

  Possible values: [order.delivery.updated]
• dataOrder

  The order, carrying its new deliveryStatus.

• 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: retries of a delivery, and the deliveries to each url you have registered. Two legitimate transitions of the same subject are two different events and carry two different ids.

  Key your idempotency on this field alone. Nothing else in the payload is a dedup key — timestamp is the moment the attempt was SENT and differs between copies of one event.

• timestampstring<date-time>

  When this delivery was SENT — not when the event happened. Order by the transported state, never by arrival.

• organization_idstring

  Your organization id, also carried on the delivery's X-Organization-ID header.

  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 — it is a value inside a body anyone who learns your url can POST. Proof of origin is the X-OneTablet-Signature header, which store-event deliveries carry on every attempt (ONE-2747); see "Verifying webhook signatures". Phase 0 order deliveries are not signed yet, so for those there is no cryptographic authentication at all.