API docs
Sous Chef Management API
Request access

Get one store

POST/management/stores/fetchStore

One storefront, by Store.id: the same Store shape fetchStores returns, addressed directly instead of paged.

Scope: exactly fetchStores' scope. 404 when storeId does not resolve for your organization. An id that does not exist and one that belongs to another organization return the same 404, the same convention as every other single-resource read on this API (fetchMenu).

Safe to retry: this operation is read-only and idempotent.

Request

application/json
required
  • storeIdstring

    Store.id, as returned by fetchStores.

Responses

200: The storefront, plus the time Sous Chef set it up.

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.

  • storeStore

    The storefront, in the same shape fetchStores returns.

  • liveAtstring<date-time>

    When Sous Chef set this storefront up, as an ISO-8601 UTC instant. It is the same value store.wentLiveAt carries. 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.

Sous Chef 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. 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 is scoped to the organization your API key resolves to, and nothing here calls out to a delivery platform live. The directory reads (fetchLocations, fetchBrands, fetchStores, fetchStore, fetchStoreHours, fetchStoreMenus) never mutate; setLocationHours and setLocationSpecialHours write a location you own.

Whether a storefront is currently taking orders is not in this section. fetchStoreStatuses, pauseStores, unpauseStores and the store.status.changed webhook are in the Store status section. This section describes what you operate. That one describes whether it is open right now, and whether the platform agrees.