Bulk Approve Sales Orders
POST/api/sales-orders/approve
Approves multiple draft (or reserved) sales orders, transitioning them to open. Newly opened orders are automatically routed for fulfillment.
orders:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Requires Bearer token.
Request body (one of ids or filters is required):
- ids (array of integers, required without filters): Sales order IDs to approve.
- filters (required without ids): Filter payload resolved against the sales-orders list — accepts the grouped
filter_groupsshape (base64-encoded JSON, same as the V2 sales-orders list) as well as the legacy JSON-string filter set. - archived (integer, optional, default 0): Used with
filters— set to 1 to include archived orders when resolving IDs.
Behavior:
- Only
draftandreservedorders can be approved; other orders are reported as errors. - An order that cannot be approved (no line items, or unmapped products) is reported as an error.
- Returns 200 when all orders approve; 200 with
warningswhen only some approve; 400 when none were selected or all failed.
Requires permission: sales_orders.approve
Request
Responses
- 200
- 400
- 401
- 403
- 422
- 429
OK
Response Headers
Bad Request
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.