CUSTOM_FIELD_FILTER_TOO_MANY_KEYS

When it happens

The filter sends more than 20 distinct custom field keys.

How to fix it

Narrow the filter to 20 keys or fewer.

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.

• GET /v1/companies/{company_id}/invoices
• POST /v1/companies/{company_id}/invoices/exports

Example response

When this error occurs, the API answers 422 Unprocessable Content with a JSON body of this shape:

{
  "type": "https://docs.beel.es/errors/CUSTOM_FIELD_FILTER_TOO_MANY_KEYS",
  "title": "CUSTOM_FIELD_FILTER_TOO_MANY_KEYS",
  "detail": "The custom fields filter accepts at most ‹value› keys per request",
  "instance": "/v1/<resource>",
  "errors": [],
  "success": false,
  "error": {
    "code": "CUSTOM_FIELD_FILTER_TOO_MANY_KEYS",
    "message": "The custom fields filter accepts at most ‹value› keys per request",
    "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