API docs
Sous Chef Management API
Request access

Unpause stores

POST/management/store-status/unpauseStores

Bring storefronts back online. Safe to repeat: unpausing an already-open store leaves it open and returns desired.state: open.

Same organization scoping and per-store independence as pauseStores. When none of the requested ids is yours, the answer is 404.

Safe to retry: this operation changes state but is idempotent.

Request

application/json
required
  • storeIdsstring[]

    Store.id values, 1-100. Chunk larger sets across calls.

Responses

200: The `desired` state just written (`open`), for each requested storefront you operate.

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.

  • statusesStoreStatus[]

    One entry per requested storefront your organization operates, carrying only storeId and the desired state just written (open). Requested ids that are not yours are omitted.

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.