---
title: "Revoke an invoice approval step"
method: POST
path: "/invoices/{id}/revoke-approval"
tags: ["invoices"]
---

# Revoke an invoice approval step

`POST /invoices/{id}/revoke-approval`

Undoes a specific user's approval step on an invoice and recalculates dependent policy tiers. Requires the `can_undo_invoice_approvals` permission.

`approval_id` is carried in the request body rather than the URL path (unlike the path shown in the original spec) — the 4-segment path documented there exceeds the max depth this API Gateway resource tree supports (3 segments; see `ottiapi/modules/api_endpoint_tree/main.tf`'s `depth_1/2/3_paths` locals).

## Path parameters

- `id` string, required

## Headers

- `Authorization` string, required
- `X-Api-Key` string, required
- `X-API-Version` string
- `Idempotency-Key` string

## Request body

- object
  - `approval_id` string, required — Object approval record ID, e.g. `pbjappr_550e8400...`

## Response `200`

Successful response with updated invoice approval state

- InvoicesPostInvoicesIdRevokeApprovalResponse200 — Empty response body

## Other responses

- `400` — Bad request - Invalid parameters or request format
- `401` — Unauthorized - Authentication required or invalid credentials
- `403` — Forbidden - Access denied or insufficient permissions

---

[API](https://skmtc.dev/ottimate/apis/api-reference.md) · [All operations](https://skmtc.dev/ottimate/apis/api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/ottimate/api-reference/revisions/ba91ff4c6969/schema)