Approves the vendor bill.

POST /accounting/vendor-bills/{id}/approve

Group: Accounting › Vendor Bills · Operation ID: approveVendorBill

Approves the vendor bill through your tenant's approval policy, which is what makes it payable and posts it to the ledger. With no approvers configured the bill goes straight to approved and posted, and with a multi-step policy it advances one step. The status after the operation is returned. A bill that is already approved is refused with STATUS_CONFLICT. A refusal from the approval framework comes back as APPROVAL_FAILED, with its own message in reason.

Open in the interactive reference

Parameters

Name	In	Type	Required	Description
`Api-Version`	header	`"v1"`	yes	The API version this request targets, named by its public identifier. Required on every request; omitting it, or naming a version this company does not have, is answered with 400. This document describes version `v1`.
`Idempotency-Key`	header	string	no	An opaque caller-chosen string (1-255 characters) that makes this request safe to retry. Repeating the same key with an identical request body replays the original response instead of re-executing - but only once that original request succeeded; a failed attempt re-executes on retry. Repeating the key with a different body is answered with 422. A key still in flight is answered with 409 - as is a key whose original request was interrupted before it finished, for a few minutes afterwards, until that attempt is presumed dead. A completed response stays replayable for 24 hours. The key is scoped to the caller, not to the action: reusing it for a different action is answered with 409 or 422 rather than treated independently. On read actions this header is ignored. On write actions that cannot offer the guarantee it is answered with `400 IDEMPOTENCY_NOT_SUPPORTED` rather than silently ignored.
`id`	path	string	yes	The unique identifier for the vendor bill to approve.

Response

200 Success

Under data (approveVendorBillOutput):

Field	Type	Required	Description
`status`	string	yes	The bill status after the operation. The approval workflow decides it, so it is read back.

Response headers

Idempotency-Replayed — Present and true only when this response replays a previously stored one for the same Idempotency-Key, rather than reflecting a live execution. Absent on a live response - never sent as false.

Errors

Code	Status
`NOT_FOUND`	400
`STATUS_CONFLICT`	400
`APPROVAL_FAILED`	400
`BILL_ALREADY_VOIDED`	400
`BILL_ALREADY_REVERSED`	400
`IDEMPOTENCY_KEY_CONFLICT`	409
`IDEMPOTENCY_PAYLOAD_MISMATCH`	422

Statuses

400 — Invalid request or business failure. Codes: NOT_FOUND, STATUS_CONFLICT, APPROVAL_FAILED, BILL_ALREADY_VOIDED, BILL_ALREADY_REVERSED
401 — Missing or invalid access token
403 — Not authorized
404 — Not found
409 — The Idempotency-Key is still being processed by another request.
422 — The Idempotency-Key was already used with a different request payload.
429 — Too many requests
500 — Internal server error