OneTablet API Documentation

fetchStoreHours

POST/management/stores/fetchStoreHours

Effective operating hours for up to 100 storefronts at a time (ONE-2622, Phase 1): 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.

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

Request

application/json
required
  • storeIdsstring[]

Responses

200 — OK
  • hoursobject[]
    • storeIdstring
    • timezonestring

      IANA timezone, e.g. America/New_York. Absent when OneTablet has none recorded.

    • regularobject[]

      The weekly template this storefront's hours resolve from: the location's, or — when every active menu at this store carries its own hours — the union of those menus' windows.

      • daystring
        Possible values: [mon, tue, wed, thu, fri, sat, sun]
      • opensAtstring
      • closesAtstring
    • specialobject[]

      Date-specific overrides — holidays, early closes.

      • datestring<date>
      • closedobject
      • opensAtstring
      • closesAtstring

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.

All three reads are org-scoped to the organization your api key resolves to, and all three are reads: nothing here mutates, and nothing here calls out to a delivery platform live (ONE-2618).