OneTablet API Documentation

fetchStore

POST/management/stores/fetchStore

One storefront, by Store.id (ONE-2719) — the same Store shape fetchStores returns, addressed directly instead of paged.

Scope: exactly fetchStores' scope, since this reuses that same query with a storeIds: [id] filter. 404 when storeId does not resolve for your organization — an id that does not exist and one that belongs to another organization are INDISTINGUISHABLE, on purpose, same convention as every other single-resource read on this API (fetchMenu).

Request

application/json
required
  • storeIdstring

    Store.id, as returned by fetchStores.

Responses

200 — OK
  • storeStore

    The storefront, in the same shape fetchStores returns.

  • liveAtstring<date-time>

    When OneTablet set this storefront up, as an ISO-8601 UTC instant. Sourced from Store."wentLiveAt" — the SAME value store.wentLiveAt carries (see its description for what it holds, and this section's header comment for why it is also surfaced at the top level). Not a go-live signal: whether the storefront is open and taking orders is fetchStoreStatuses.

About Stores

The places you operate and the brands you operate there.

OneTablet models a restaurant business in three layers, and every other section of this API assumes them. A brand is a menu concept — what a customer sees on a delivery app. A location is a physical address with a kitchen in it. A store is one storefront: a single brand, at a single location, on a single platform — so a location running two brands on three platforms has six stores, each with its own menu, hours and pause state.

The directory reads join on IDS, never on display names: every store carries its location.id and brand.id, and a location carries the id of each brand it runs.

Start here — a location carries the timezone that every schedule, report window and business day elsewhere on this API is interpreted in.

EVERY operation here is a READ, org-scoped to the organization your api key resolves to: nothing in this section mutates, and nothing here calls out to a delivery platform live (ONE-2618).

Whether a storefront is currently taking orders is NOT here — fetchStoreStatuses, pauseStores, unpauseStores and the store.status.changed webhook live in StoreStatusApi under /management/store-status (ONE-2736). This section answers "what do I operate"; that one answers "is it open right now, and does the platform agree".