All order endpoints require authentication.Documentation Index
Fetch the complete documentation index at: https://docs.laportenard.com/llms.txt
Use this file to discover all available pages before exploring further.
Create or update order
POST
/pos-api/v1/orders/createpos_reference returns the existing order.
Key fields
| Field | Type | Description |
|---|---|---|
pos_reference | string | Unique order reference (idempotency key) |
table_id | integer | Floor plan table ID |
lines | array | Order line items |
fiscal_type | string | NCF fiscal type for Dominican tax |
The
pos_reference field is the idempotency key. Duplicate submissions with the same reference are safe and return the existing order.Reserve NCF
POST
/pos-api/v1/orders/reserve-ncfHub batch sync
POST
/pos-api/v1/hub/batch-syncHub order finalization
POST
/pos-api/v1/hub/finalizecreate_from_ui) inside a database savepoint.
Behaviors
| Behavior | Detail |
|---|---|
| Savepoint | create_from_ui runs inside self.env.cr.savepoint() — any failure rolls back atomically, preventing phantom draft orders |
| Default partner | When no customer is provided, falls back to config.default_partner_id |
| Payment verification | After creation, verifies statement_ids are present; raises if empty |
| Idempotency | Same pos_reference returns the existing paid order |
| Fiscal pipeline | Full NCF/DGII processing (same as direct API orders) |
Response
Audit
Each hub finalization is logged as ahub_finalize event in the nu_restaurant_pos.order_audit model.