Get one store's status
Status for one storefront: the single-store form of fetchStoreStatuses, returning the same three things: desired, observed, discrepancy.
The status is identical to the one the bulk read returns. Every caveat on fetchStoreStatuses applies here unchanged, and lastPolledAt is still the field that tells you how fresh observed is.
Not found is 404, and covers two cases, matching the bulk read, which omits the same store from the page:
- the
storeIddoes not exist, or belongs to another organization (the two are not distinguished, as everywhere else on this API), and - the storefront is yours but Sous Chef has never polled it, so there is no observation to report. The response message says which of the two applies. The status code does not, because in both cases there is no status to return.
If you need the storefront's identity rather than its status, fetchStores answers for a never-polled store where this one does not.
Safe to retry: this operation is read-only and idempotent.
Request
- storeIdstring
The
Store.idto read.
{
"storeId": "00000000-0000-0000-0000-000000000000"
}Responses
Headers
- x-mealco-tx-idstringoptional
The correlation id for this call, returned on every response that an operation produces, successful or not. Quote it when you report a problem so that we can trace the request. You may send your own x-mealco-tx-id on the request and it is used as the id. It is optional in the schema because a request with a malformed JSON body is rejected before an id is assigned, so that one response carries neither this header nor the txId field of the error body.
- statusStoreStatus
The storefront's status: the same
StoreStatusthe bulk read returns. It is wrapped in an object, not returned bare, so that sibling fields can be added without a breaking change.
{
"status": {
"storeId": "00000000-0000-0000-0000-000000000000",
"desired": {
"state": "open",
"pauseReason": "closingEarly",
"pauseNote": "<pauseNote>",
"pausedUntil": "2026-01-01T00:00:00Z",
"updatedAt": "2026-01-01T00:00:00Z"
},
"observed": {
"state": "online",
"orderable": true,
"platformReason": "<platformReason>"
},
"discrepancy": {
"hasDiscrepancy": true,
"classification": "pauseNotPropagated",
"autoRemediable": true,
"requiresHumanIntervention": true,
"remediationChannel": "api"
},
"lastPolledAt": "2026-01-01T00:00:00Z"
}
}About Store status
Whether each storefront is actually taking orders, and whether Sous Chef and the delivery platform agree about it.
Separate from Stores, which is the identity map: the brands, kitchens and storefronts you operate, which changes when your estate changes. This section is the operational layer on top of it: two reads (fetchStoreStatuses, fetchStoreStatus), two writes (pauseStores, unpauseStores) and the store.status.changed webhook, all addressed by the Store.id values fetchStores returns. It uses the same API key, organization scoping and ids, under a different route prefix (/management/store-status).
Three things are kept distinct throughout: desired is what Sous Chef is configured to do, observed is what the platform reports, and discrepancy is the classified disagreement between the two.
Scoped to the organization your API key resolves to, exactly as the directory reads are.