Batch Decide Approval Cards
POST/api/support/agent/approvals/batch-decide
Approves several status cards in one go — the low-risk "mark this resolved / close this duplicate" proposals. All or nothing: if any card is not a status card the request is refused with a 422 and nothing is decided; if any card is no longer open (already decided or superseded) it is refused with 409, data carries that card, and nothing is decided. Every other kind of card must be decided one at a time with Decide Approval Card.
support:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Each approved card records an approval_decided event on its ticket, exactly as a single decision would.
Request body
ids[](array of integers, required, 1–100, distinct) — the card idsaction(string, required) — must beapprove
The response is the decided cards, as a plain array (fields as in List Approval Cards).
Authentication: Bearer token with the support:write scope, or an authenticated session, from a caller with an active support role that can work tickets — a viewer is refused with 403. No tenant context — this endpoint is central.
Request
Responses
- 200
- 401
- 403
- 409
- 422
- 429
OK
Response Headers
Unauthorized
Response Headers
Forbidden
Response Headers
Conflict
Response Headers
Unprocessable Content
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.