Supplier invoices

Void a supplier invoice

Voids an already VALIDATED received invoice with a reason, which is required and is kept.

POST
/api/v1/supplier-invoices/{supplierInvoiceId}/void

Request examples

curl https://app.filmo.io/api/v1/supplier-invoices/supp_8f2a1c/void \
  --request POST \
  --header "Authorization: Bearer $FILMO_API_KEY" \
  --header "Idempotency-Key: $(uuidgen 2>/dev/null || cat /proc/sys/kernel/random/uuid)" \
  --header 'Content-Type: application/json' \
  --data '{
  "reason": "Llegó duplicada; la buena es la del 3 de septiembre"
}'
{
  "data": {
    "id": "supplier_invoice_9f3a2b",
    "supplierInvoiceNumber": "2026-0001",
    "status": "Example status",
    "createdAt": "2026-09-01T08:00:00.000Z",
    "updatedAt": "2026-09-01T08:00:00.000Z"
  }
}

Generated from the schema

Not reversible

Voiding takes the document to voided, and no operation undoes it.

It keeps its internal number —voiding does not release the numbering— and moves to voided. Only from validated: a draft is deleted from the application, not voided. It does not touch the treasury payment that may have paid it or the purchase order that originated it. It requires the purchases add-on (402 without it). Returns the full invoice, the same projection as its GET.

Authorizations

Bearer API key with the scope below. supplier-invoices:write

Headers

Idempotency-Keystring

Unique identifier of the request, chosen by the client (a UUID works). Between 1 and 255 characters: an empty header is rejected with 400 validation_error, because the client would believe itself protected. Repeating the same key with the SAME body within 24 h returns the stored response without executing again, with the Idempotent-Replay: true header. With a DIFFERENT body it returns 422. It is the safe way to retry after a network timeout.

Limits: min length 1, max length 255

Example:"9f1c2f4e-3a5b-4f6d-8e7a-0b1c2d3e4f5a"

If-Matchstring

Optimistic locking: the ETag you read from the resource (or *). If the resource changed since, the write is rejected with 412 precondition_failed before doing anything; read it again and retry. Without the header the write always proceeds.

Example:"\"3sT3d9pBvZq4h2N0w8x1YkLmQ7c\""

Path parameters

supplierInvoiceIdstringRequired

Supplier invoice identifier.

Limits: min length 1

Body

application/json

Body schema: SupplierInvoiceVoidBody

reasonstringRequired

Reason for voiding. It is stored on the invoice and in its history.

Limits: min length 1, max length 500

Response

application/json

Successful response.

Response schema: SupplierInvoiceDto

Envelope: SupplierInvoiceResponse. meta.warnings is present only when the operation is deprecated.

Headers: X-Request-Id · RateLimit-Limit · RateLimit-Remaining · RateLimit-Reset · ETag · Idempotent-Replay

dataobject

Invoice received from a supplier.

Show child attributes
data.idstring

Supplier invoice identifier.

data.supplierInvoiceNumberstring | null

Number the supplier put on the invoice; null if it was not recorded.

data.statusstring

Status of the invoice within the purchasing cycle.

data.createdAtstring<date-time>

Creation date in ISO 8601 UTC.

data.updatedAtstring<date-time>

Last modification date in ISO 8601 UTC.

metaobject

Additional information about the response.

Show child attributes
meta.warningsobject[]

Lifecycle warnings; present only when the operation is deprecated.

Show child attributes
meta.warnings.codestring

Stable warning code.

Available options: deprecated

meta.warnings.messagestring

For people: what is deprecated, until when, and what to use.

meta.warnings.sunsetstring

Day (YYYY-MM-DD) the operation stops being served.

meta.warnings.replacementstring | null

operationId of the operation to use instead, or null if there is none.

Errors

StatusCodesMeaning
400validation_errorMalformed query or body. errors[] lists every offending field with its stable code.
402addon_requiredThe account plan does not include the add-on this operation needs; requiredAddon names it.
404not_foundIt does not exist or is outside the scope of the API key.
409conflictThe current state of the resource prevents the operation, a request with that Idempotency-Key is already in progress, or another conditional write (If-Match) held the resource for more than five seconds. errors[0].code says which: in_progress and lock_timeout are solved by retrying; invalid_state is not, because the state of the resource forbids the operation.
412precondition_failedThe If-Match entity tag does not match the current representation. Read the resource again and retry.
422idempotency_key_reusedThe same key was used before with a different body. Change the key.

401, 403, 429, 500 can be returned by any operation. Errors

Deprecation

This operation is not deprecated. Deprecations are announced with a Deprecation header and a sunset date. Versioning policy