POS action service
Syntax of requests is almost the same, for better flexibility we are using only one endpoint for all POS actions.
Create order
Info
POST /api/action/:cloudId/:branchId/order/create
Success
POST /v2/clouds/:cloudId/branches/:branchId/pos-actions
Update order
Info
POST /api/action/:cloudId/:branchId/order/update
Success
POST /v2/clouds/:cloudId/branches/:branchId/pos-actions
Issue order
Info
POST /api/action/:cloudId/:branchId/order/issue
Success
POST /v2/clouds/:cloudId/branches/:branchId/pos-actions
Issue and pay order
Info
POST /api/action/:cloudId/:branchId/order/issue-and-pay
Success
POST /v2/clouds/:cloudId/branches/:branchId/pos-actions
Pay order
Info
POST /api/action/:cloudId/:branchId/order/pay
Success
POST /v2/clouds/:cloudId/branches/:branchId/pos-actions
Add order item
Info
POST /api/action/:cloudId/:branchId/order/add-item
Success
POST /v2/clouds/:cloudId/branches/:branchId/pos-actions