Skip to main content

Override Approval Request

POST 
/api/approval-requests/:approvalRequest/override

Complete a pending approval request as an administrator who is not an eligible approver — for example when nobody eligible is available. Every remaining step is marked approved, the request is flagged overridden, the decision is recorded as override_approved with your reason, and the requester and everyone who could have approved are notified.

Required scope: purchase-orders:write

Grant 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). Requires administrator access (or the approval_policies.override permission).

Body fields:

  • reason (string, required, 10–1000 characters)

Error responses carry a machine-readable code next to the human message:

  • 403 approval_limit_exceeded — you are not eligible for the current step (over your limit, your own request under separation of duties, or you already decided this step). Other 403 codes: approval_withdraw_forbidden, approval_remind_forbidden, approval_override_forbidden, approval_reroute_forbidden.
  • 409 approval_state_conflict — the request is no longer pending (already approved, rejected, withdrawn, or superseded by a newer request after the document changed). Re-read it and act on the current request.
  • 404 — the approval request does not exist.

Request​

Responses​

OK

Response Headers
    Content-Type