Purpose
Return a specific order so you can inspect its metadata, customer, payment, and fulfillment status without fetching the entire list.HTTP Request
Path Parameters
Unique identifier of the order (
ORD-12345, UUID, or numeric ID depending on your tenant).Query Parameters
Include related resources in the response. Currently supported:
receipt:id,service_notification_id,status.
When included, the data.receipt field will be present in the response (or null if no receipt exists for the order).Request Example
Response
200 OK — Order found
404 Not Found — Order does not exist
Field Reference
| Field | Type | Description |
|---|---|---|
id | number | Order identifier returned during creation or list operations. |
venue_id | number | Venue that owns the order. |
type | string | Source of the order (for example, CALL_CENTER_ORDER). |
integration_status | string | State reported by the upstream integration. |
status | string | Current lifecycle state (PENDING, RECEIVED, IGNORE, DELIVERED). |
payload | object | Full payload captured during creation (service, customer, products, meta). |
payload.customer.id | number | Linked customer record (if available). |
payload.products[] | array | Breakdown of products, modifiers, and totals. |
receipt | object | null | Present when with[0]=receipt:... is provided. Contains minimal receipt data or null if no receipt exists. |
created_at | string | Creation timestamp (ISO 8601). |
updated_at | string | Last update timestamp (ISO 8601). |
Notes
- Returns the same structure as the list endpoint, providing parity between detail and collection responses.
- Use this endpoint after receiving webhook notifications to hydrate UI with complete order data.
- You can embed the linked receipt using the
with[0]parameter. If the order has no receipt,receiptwill benull. - Combine with the receipts endpoint when you need final settlement information once the order is delivered.