Get store menu assignments

POST/management/stores/fetchStoreMenus

Which menus are assigned to each of up to 100 storefronts, each menu's operating-hours configuration, whether and when it was last published, and — where a published snapshot exists — the menu document exactly as last published to that storefront.

Snapshots are returned verbatim from OneTablet's publish history, never regenerated; a menu never published to the store carries no snapshot, and neither does one whose recorded snapshot exceeds this API's size cap (see MenuAssignment.snapshot).

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 menu assignments for, 1-100.

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

Responses

200 — The menus assigned to each requested storefront your organization operates.

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.

assignmentsStoreMenuAssignments[]
One entry per requested storefront your organization operates that has at least one menu assigned, in request order. Requested ids that are unknown, deactivated, not yours, or have no menu assigned are omitted.

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 is org-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 here — fetchStoreStatuses, pauseStores, unpauseStores and the store.status.changed webhook live in the Store status section. This section answers "what do I operate"; that one answers "is it open right now, and does the platform agree".