API docs
Sous Chef Management API
Request access

Get store hours

POST/management/stores/fetchStoreHours

Effective operating hours for up to 100 storefronts at a time: regular weekly windows plus special dates (holidays, early closes), resolved in each location's timezone. Windows may cross midnight. Compare against your own expected hours to detect drift.

A storefront whose active menus all carry their own hours reports the union of those menus' windows as regular; otherwise the location's weekly hours are reported.

Two exceptions. An organization whose brands cook in a kitchen it does not own can set its own weekly hours for all of its brands there, in the Sous Chef Portal. Once it has, those hours replace the location's in regular on its storefronts there. The location's special dates still reach those storefronts: a closure still closes them, and a date that opens the kitchen opens each one only within the hours it reports as regular. Whoever reads those storefronts gets this same answer, the kitchen's owner included: on them, regular is not the week the owner set with setLocationHours.

A single brand can also keep its own week at a location. That week then replaces whichever hours would otherwise apply in regular on that brand's storefronts there.

No pagination. Pass 1-100 storeIds and chunk a larger estate across calls.

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

Request

application/json
required
  • storeIdsstring[]

    Store.id values to read hours for, 1-100.

Responses

200: The effective hours of each requested storefront your organization operates.

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.

  • hoursStoreHours[]

    One entry per requested storefront your organization operates. Requested ids that are unknown, deactivated or not yours are omitted rather than reported as errors.

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.