CUSTOM_FIELD_ARCHIVED

When it happens

A key in custom_fields names a field the company has archived.

How to fix it

Reactivate it with "is_archived": false, or send the list without it.

Retry

Not as is: the same request fails the same way. Fix the cause described above, then send the request again, under a new Idempotency-Key if the body changed.

Returned by

The operations where this code is most likely. The list is not exhaustive.

• POST /v1/companies/{company_id}/invoices
• PATCH /v1/companies/{company_id}/invoices/{invoice_id}

Example response

When this error occurs, the API answers 409 Conflict with a JSON body of this shape:

{
  "type": "https://docs.beel.es/errors/CUSTOM_FIELD_ARCHIVED",
  "title": "CUSTOM_FIELD_ARCHIVED",
  "detail": "The custom field ‹value› is archived and cannot be added to an invoice",
  "instance": "/v1/<resource>",
  "errors": [],
  "success": false,
  "error": {
    "code": "CUSTOM_FIELD_ARCHIVED",
    "message": "The custom field ‹value› is archived and cannot be added to an invoice",
    "details": {}
  },
  "meta": {
    "timestamp": "2026-05-21T10:00:00Z",
    "request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
  }
}

The type URI is stable and always resolves to this page.

Message

Send the request with Accept-Language: <es|en|ca> to receive the message in your preferred language.

Placeholders like ‹value› are filled in at runtime with the actual values of your request.

Other errors in this category

Keep exploring