Bulk Approve Approval Requests
POST/api/approval-requests/bulk-approve
Approve several approval requests as the signed-in user. Each request is checked on its own: ones you are not eligible for, or that are no longer pending, are skipped with the reason — the rest are approved (for a multi-step request, your approval completes your step and the request moves on).
purchase-orders:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Requires Bearer token with the purchase-orders scope (read for GET, write for POST/PUT/DELETE). Rate limited to 30 calls per minute.
Body fields:
ids(array of integers, required, 1–500) — approval request IDsnotes(string, optional, max 1000) — recorded on every decision
Response: up to 25 IDs are processed inline and return 200 with data.approved (IDs) and data.skipped (id, document, reason). More than 25 IDs return 202 with data.tracked_job_log_id; follow progress with GET /api/tracked-job-logs/{trackedJobLog}.
Request
Responses
- 200
- 202
- 401
- 403
- 422
- 429
OK
Response Headers
Accepted
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.
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.