Documentation Index
Fetch the complete documentation index at: https://developer.clopos.com/llms.txt
Use this file to discover all available pages before exploring further.
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 (numeric ID).
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
Order Object
| Field | Type | Description |
|---|---|---|
id | integer | Order identifier. |
venue_id | integer | Venue that owns the order. |
type | string | Source of the order (e.g., CALL_CENTER_ORDER). |
integration | string | Integration channel that created the order (e.g., call_center_new). |
integration_uuid | string (nullable) | UUID assigned by the integration source. |
integration_id | string (nullable) | External ID from the integration source. |
integration_status | string | State reported by the upstream integration (e.g., CREATED). |
customer_ref_id | string (nullable) | External customer reference ID from the integration. |
status | string | Current lifecycle state: PENDING, RECEIVED, IGNORE, DELIVERED. |
payload | object | Full order content including service, customer, products, and meta. |
payload.service | object | Sale type and venue for the order. |
payload.customer | object | Customer details (id, phone, address, name). |
payload.products | array | Line items with product_id, count, modifiers, and pricing meta. |
payload.meta | object | Order-level metadata: comment, discount, service charge settings. |
integration_response | object (nullable) | Response data from the integration, if any. |
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.