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
POST /api/action/:cloudId/:branchId/order/create
POST /v2/clouds/:cloudId/branches/:branchId/pos-actions
Update order
POST /api/action/:cloudId/:branchId/order/update
POST /v2/clouds/:cloudId/branches/:branchId/pos-actions
Issue order
POST /api/action/:cloudId/:branchId/order/issue
POST /v2/clouds/:cloudId/branches/:branchId/pos-actions
Issue and pay order
POST /api/action/:cloudId/:branchId/order/issue-and-pay
POST /v2/clouds/:cloudId/branches/:branchId/pos-actions
Pay order
POST /api/action/:cloudId/:branchId/order/pay
POST /v2/clouds/:cloudId/branches/:branchId/pos-actions
Add order item
POST /api/action/:cloudId/:branchId/order/add-item
POST /v2/clouds/:cloudId/branches/:branchId/pos-actions

OAuth2 Login Service

Product Service

Last modified 2yr ago