Reservation widget
What an embeddable widget on your own site calls. Every route takes a `fields` parameter because the widget runs on a guest’s connection: it asks for the columns it renders instead of downloading the whole record.
/public/restaurants/{slug}/widget-config スコープ: public (no key)Returns what the widget needs to render itself for this restaurant before the guest interacts with it. Fetch it once on load rather than hard-coding the values into your page, so a change made in Tablezio reaches the widget without a redeploy.
slugstring必須Restaurant slug.
リクエスト
curl 'https://api.tablezio.com/public/restaurants/casa-pepe/widget-config'/public/restaurants/{slug}/menu スコープ: public (no key)The menu for an embedded surface, with field selection, category filtering, availability filtering, paging and language. `lang` picks the translated names and descriptions stored on the item, so a multilingual menu is one request with a different parameter, not a second menu.
slugstring必須Restaurant slug.
fieldsstring任意Comma-separated item fields to return.
categoryFieldsstring任意Comma-separated category fields to return.
categorystring任意Restrict to one category.
availableboolean任意Only return currently available items.
limitinteger任意Page size.
offsetinteger任意Offset into the result set.
langstring任意Language for translated names and descriptions.
リクエスト
curl 'https://api.tablezio.com/public/restaurants/casa-pepe/menu?available=true&lang=es&limit=50'/public/restaurants/{slug}/menu/categories スコープ: public (no key)Just the categories, with field selection and language. Use it to render the menu navigation before pulling the items for the category the guest opens.
slugstring必須Restaurant slug.
fieldsstring任意Comma-separated category fields to return.
langstring任意Language for translated names.
リクエスト
curl 'https://api.tablezio.com/public/restaurants/casa-pepe/menu/categories?lang=fr'/public/restaurants/{slug}/menu/items/{itemId} スコープ: public (no key)One menu item, for the detail view a guest opens from the list. Field selection applies here too, so the detail request can ask for the fields the list omitted rather than refetching everything.
slugstring必須Restaurant slug.
itemIdstring必須Menu item id.
fieldsstring任意Comma-separated fields to return.
langstring任意Language for translated name and description.
リクエスト
curl 'https://api.tablezio.com/public/restaurants/casa-pepe/menu/items/5a1b2c3d4e5f6a7b8c9d0e1f'/public/restaurants/{slug}/reservations/availability スコープ: public (no key)Returns bookable slots for a date. `partySize` matters because availability is computed against real tables and their capacities, not against a flat cover count; `from`, `to` and `slotInterval` shape the grid the widget renders.
slugstring必須Restaurant slug.
datestring必須Date to check, ISO `YYYY-MM-DD`.
partySizeinteger任意Number of covers. Availability is computed against table capacity.
fromstring任意Earliest time of day to consider.
tostring任意Latest time of day to consider.
slotIntervalinteger任意Minutes between slots.
fieldsstring任意Comma-separated fields to return.
リクエスト
curl 'https://api.tablezio.com/public/restaurants/casa-pepe/reservations/availability?date=2026-10-04&partySize=4'/public/restaurants/{slug}/reservations スコープ: public (no key)Books one of the slots returned by the availability endpoint. The booking is written straight into the restaurant’s reservation records, which is the difference between an embedded widget and a third-party booking channel: there is nothing to reconcile afterwards, and no per-cover fee in between.
slugstring必須Restaurant slug.
リクエスト
curl -X POST 'https://api.tablezio.com/public/restaurants/casa-pepe/reservations' \
-H 'Content-Type: application/json' \
-d '{"name":"Ana","email":"[email protected]","partySize":4,"date":"2026-10-04","time":"21:00"}'