Unpause stores

POST/management/store-status/unpauseStores

Bring storefronts back online. Idempotent — unpausing an already-open store is a no-op that still returns its current status.

Same org-scoping and per-store independence as pauseStores.

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.

{
  "storeIds": [
    "<storeIds>"
  ]
}

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, echoed on every response — a 200 exactly as much as a 400, 401 or 500. Quote it when reporting a problem and we can find every log line for the request, in every service it touched. You may also send your own x-mealco-tx-id on the request and we adopt it, so your correlation id becomes ours. Not marked required for one reason: a request whose JSON body is malformed is rejected before it reaches an operation, so no id exists yet and that single response carries neither this header nor the txId field of the error body. Everything that reaches an operation carries it.

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 OneTablet 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 — one read (fetchStoreStatuses), two writes (pauseStores, unpauseStores) and the store.status.changed webhook — all addressed by the Store.id values fetchStores hands you. Same api key, same org scoping, same ids; a different job, and a different route prefix (/management/store-status) so the url says which.

Three things are kept distinct throughout, and conflating them is the mistake this section exists to prevent: desired is what OneTablet is configured to do, observed is what the platform reports, and discrepancy is the classified disagreement between the two.

Org-scoped to the organization your api key resolves to, exactly as the directory reads are.