Order operations

Kitchen, delivery and status transitions

The operational order surface, authenticated with an X-API-Key widget key. It pages with page/limit and projects with `fields`, unlike the versioned /v1/orders resource — use these for live screens, and /v1/orders for integrations.

List orders

GET

/public/orders Escopo: X-API-Key (widget key)

Lists orders for the restaurant the key belongs to, with offset paging and sorting. `fields` selects the projection — the default is a compact set (id, orderNumber, type, status, total, createdAt) rather than the whole order, because these screens refresh often.

Parâmetros de consulta

fieldsstringOpcional

Comma-separated fields. Defaults to id,orderNumber,type,status,total,createdAt.

statusstringOpcional

Filter by order status.

typestringOpcional

Filter by order type.

pageintegerOpcional

Page number, 1-based.

limitintegerOpcional

Page size.

sortstringOpcional

Field to sort on, e.g. createdAt.

orderstringOpcional

Sort direction.

ascdesc

Requisição

curl 'https://api.tablezio.com/public/orders?status=placed&limit=20' \
  -H 'X-API-Key: tbz_…'

Active orders

GET

/public/orders/active Escopo: X-API-Key (widget key)

The orders currently in play, without you having to know which statuses count as active. Poll this one for a floor or expo screen instead of filtering the full list client-side.

Parâmetros de consulta

fieldsstringOpcional

Comma-separated fields to return.

Requisição

curl 'https://api.tablezio.com/public/orders/active' -H 'X-API-Key: tbz_…'

Kitchen orders

GET

/public/orders/kitchen Escopo: X-API-Key (widget key)

The kitchen view, optionally narrowed to one station. Station routing is stored on the menu category, so an item reaches this list already assigned — the screen filters, it does not decide.

Parâmetros de consulta

fieldsstringOpcional

Comma-separated fields to return.

stationstringOpcional

Restrict to one kitchen station.

Requisição

curl 'https://api.tablezio.com/public/orders/kitchen?station=grill' \
  -H 'X-API-Key: tbz_…'

Active deliveries

GET

/public/orders/delivery/active Escopo: X-API-Key (widget key)

The delivery orders currently out or waiting to go out — the board a dispatcher watches. Same field selection as the other list views.

Parâmetros de consulta

fieldsstringOpcional

Comma-separated fields to return.

Requisição

curl 'https://api.tablezio.com/public/orders/delivery/active' -H 'X-API-Key: tbz_…'

Track a delivery

GET

/public/orders/delivery/{id}/track Escopo: X-API-Key (widget key)

Tracking state for one delivery order, resolved through the delivery fleet service. Use it to drive a per-order tracking view rather than polling the whole active board.

Parâmetros de caminho

idstringObrigatório

Order id.

Parâmetros de consulta

fieldsstringOpcional

Comma-separated fields to return.

Requisição

curl 'https://api.tablezio.com/public/orders/delivery/507f1f77bcf86cd799439011/track' \
  -H 'X-API-Key: tbz_…'

Retrieve an order

GET

/public/orders/{id} Escopo: X-API-Key (widget key)

One order, scoped to the restaurant the key resolves to — an id from another restaurant does not resolve. Ask for the fields the detail view needs; the list endpoints deliberately return less.

Parâmetros de caminho

idstringObrigatório

Order id.

Parâmetros de consulta

fieldsstringOpcional

Comma-separated fields to return.

Requisição

curl 'https://api.tablezio.com/public/orders/507f1f77bcf86cd799439011' \
  -H 'X-API-Key: tbz_…'

Create an order

POST

/public/orders Escopo: X-API-Key (widget key)

Creates an order on the operational surface. If you are building an integration rather than a screen, prefer `POST /v1/orders`: it is the versioned resource, it supports idempotency keys and expansions, and it is the one covered by the API changelog.

Requisição

curl -X POST 'https://api.tablezio.com/public/orders' \
  -H 'X-API-Key: tbz_…' \
  -H 'Content-Type: application/json' \
  -d '{"type":"dine-in","items":[{"menuItemId":"5a1b2c3d4e5f6a7b8c9d0e1f","quantity":1}]}'

Update order status

PATCH

/public/orders/{id}/status Escopo: X-API-Key (widget key)

Moves the whole order to a new status. This is the transition a floor or expo screen fires; the allowed values are validated server-side, so an unknown status is a 400 rather than a silently stored string.

Parâmetros de caminho

idstringObrigatório

Order id.

Parâmetros do corpo

statusstringObrigatório

New order status.

Requisição

curl -X PATCH 'https://api.tablezio.com/public/orders/507f1f77bcf86cd799439011/status' \
  -H 'X-API-Key: tbz_…' \
  -H 'Content-Type: application/json' \
  -d '{"status":"ready"}'

Update an order item status

PATCH

/public/orders/{id}/items/{itemIndex}/status Escopo: X-API-Key (widget key)

Moves a single line of the order — addressed by its index, not by an id, because an order item is a position in the order rather than a standalone record. The accepted values are pending, preparing, ready and served, which is what makes a per-station display possible: each station advances only its own lines.

Parâmetros de caminho

idstringObrigatório

Order id.

itemIndexintegerObrigatório

Zero-based index of the item within the order.

Parâmetros do corpo

statusstringObrigatório

New item status.

pendingpreparingreadyserved

Requisição

curl -X PATCH 'https://api.tablezio.com/public/orders/507f1f77bcf86cd799439011/items/0/status' \
  -H 'X-API-Key: tbz_…' \
  -H 'Content-Type: application/json' \
  -d '{"status":"ready"}'