Revise invoice administrative routing
Append an administrative routing revision to an issued or overdue invoice.
- Supply administrative_centres (including [] to select none), a nonblank reason of at most 500 characters and the current expected_version in the body.
- Missing version returns 428; a stale version returns 409 with current_version only after authorization.
- A successful append returns 201 and its committed administrative_version.
- Parent invoice If-Match does not replace the body precondition.
- Fiscal data, issuance, payment terms and delivery are unchanged; no invoice is emailed or submitted by this operation.
Your API key as a bearer token: fact_live_… in production, fact_test_… in sandbox. See the authentication guide.
In: header
Path Parameters
Public identifier (UUID v7) of the company. Get it from GET /v1/me (data.scope[].id).
uuidPublic identifier (UUID v7) of the invoice.
uuidHeaders
Client-generated opaque key (up to 255 characters; UUID v7 recommended) that makes retries safe: the first response is cached and replayed for repeats without re-executing the mutation. Reusing a key with a different body returns 422 idempotency_key_reused; the values of secret fields (password, secret…) count as part of the body, so retrying with a corrected secret under the same key is a different request, never the replay of the earlier answer. See the Idempotency guide.
1 <= length <= 255Pin the API version (YYYY-MM-DD, Stripe-style date versioning) for this request; omit to use the key's pinned version, or the latest if none. Unsupported version → 400 unsupported_api_version; malformed → 400 parameter_invalid_format. The effective version is echoed in the Factuarea-Version response header. See the Versioning guide.
dateRequest Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json