Item availability changed
Items were 86'd or restocked at a kitchen that sells them through your stores.
Delivered to the ONE url you registered, alongside every other event you subscribed it to — subscribe it to item.availability.changed with setAllWebhookSettings. Return any 2xx to acknowledge; anything else is retried with exponential backoff. Deduplicate on the envelope's id.
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: 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 —
timestampis the moment the attempt was SENT and differs between copies of one event. - eventstring
Always
item.availability.changed.Possible values: [item.availability.changed] - 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-IDheader.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-Signatureheader, which store-event deliveries carry on every attempt; see "Verifying webhook signatures". Deliveries to an endpoint on the current delivery pipeline (every order endpoint registered for order intake, and every store event) are always signed. Order deliveries to an endpoint still on the older pipeline are not signed yet, so for those there is no cryptographic authentication at all. - dataItemAvailabilityChange
The change.
{
"id": "00000000-0000-0000-0000-000000000000",
"event": "item.availability.changed",
"timestamp": "2026-01-01T00:00:00Z",
"organization_id": "00000000-0000-0000-0000-000000000000",
"data": {
"locationId": "00000000-0000-0000-0000-000000000000",
"stores": [
{
"storeId": "00000000-0000-0000-0000-000000000000",
"storeCode": "<storeCode>"
}
],
"items": [
{
"itemId": "00000000-0000-0000-0000-000000000000",
"sku": "<sku>",
"name": "<name>",
"isModifier": true,
"available": true
}
],
"changedAt": "2026-01-01T00:00:00Z"
}
}About Item availability
Item availability ("86-ing") — mark one item available or unavailable at one kitchen.
fetchLocationItems and setItemAvailability work as a pair: the write needs the discovery read, because Sous Chef's item ids cannot be known in advance.
There is no Idempotency-Key replay on this API: a retried setItemAvailability call re-applies the same value rather than de-duplicating.