Skip to main content

Re-route Approval Request

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

Re-evaluate a pending approval request against the current policy — after the policy was edited, an approver left, or nobody is eligible. The original request is marked superseded (its superseded_by_id points at the new one) and a new pending request with reason reroute is returned. Approvals already given on a step whose approver list is unchanged carry over.

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). No body.

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