Request Purchase Order Approval
POST/api/purchase-orders/:purchase_order/request-approval
Submit a draft purchase order for approval. Notifies every user who holds the purchase_orders.approve permission. The purchase order must be a draft with at least one line, and must not already have a pending request.
purchase-orders:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Requires Bearer token.
Requires permission: purchase_orders.update
The optional notes field (max 1000 characters) is shown to approvers with the request. The response includes notified_approvers — the number of users notified.
Approval policy:
While the purchase-order approval policy is enabled the request is routed by amount to the policy's eligible approvers instead of everyone holding purchase_orders.approve; notified_approvers counts them. The pending request is then visible at GET /api/approval-requests/for/purchase_order/{id} and can be decided there or with the endpoints below.
Request
Responses
- 200
- 401
- 403
- 404
- 409
- 422
- 429
OK
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.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Conflict
Response Headers
Unprocessable Entity
Response Headers
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.