Purpose
Fetches the statuses, customer details, and line items of your multi-channel orders in a single request.HTTP Request
Authorization
This request requires three custom headers:x-token: Your authentication tokenx-brand: The brand code you want to accessx-venue: The branch ID to operate on
Request Example
Response
200 OK — Orders list
400 Bad Request — Invalid filters
401 Unauthorized — Authentication is missing or invalid
429 Too Many Requests — Limit exceeded
Field Reference
| Field | Type | Description |
|---|---|---|
id | string | Order identifier. |
status | string | Current lifecycle state. accepted orders are sent to the POS. |
receipt_id | number | Linked open receipt ID once the POS accepts the order. |
payment_status | string | Payment state (e.g., pending, paid). |
total | number | Order grand total. |
created_at | string | Creation timestamp (ISO 8601). |
updated_at | string | Last update timestamp (ISO 8601). |
Notes
- When an order is created through this endpoint, the POS receives a push notification and notifies the clerk of the new order. Accepted orders automatically transition into open receipts.
- Use
status=pendingto monitor orders awaiting POS confirmation. - Poll or subscribe to webhooks to track further status changes if your integration requires real-time updates.
Authorizations
Access token obtained from /auth endpoint
Brand identifier
Venue identifier
Query Parameters
Maximum number of orders to return (1-100)
Required range:
1 <= x <= 100Filter by order status
Available options:
pending, confirmed, completed, cancelled