unpauseStores
Bring storefronts back online (ONE-2620). 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.
Request
- storeIdsstring[]
Store.idvalues, 1-100. Chunk larger sets across calls.
{
"storeIds": [
"<storeIds>"
]
}Responses
- statusesStoreStatus[]
One entry per requested storefront your organization operates, carrying only
storeIdand thedesiredstate 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.
SPLIT OUT OF Stores BY ONE-2736. Stores 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.