NewProvince is only required for addresses in Spain
BeeL
Get startedMulti-NIFVeriFactuRulesStripeAPI referenceChangelog
ErrorsAll codes

CUSTOMER_FIELD_INVALID_FORMAT

Invalid format for '‹value›': expected ‹value›


Category: Customers

RetryAfter fixing the cause

When it happens

A field of a row does not have the expected format. The message names the field and the format expected. It is reported in the row's errors.

How to fix it

Correct the value in that row.

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.

Example response

When this error occurs, the API returns a JSON response with the following shape:

{
  "type": "https://docs.beel.es/errors/CUSTOMER_FIELD_INVALID_FORMAT",
  "title": "CUSTOMER_FIELD_INVALID_FORMAT",
  "detail": "Invalid format for '‹value›': expected ‹value›",
  "instance": "/v1/<resource>",
  "errors": [],
  "success": false,
  "error": {
    "code": "CUSTOMER_FIELD_INVALID_FORMAT",
    "message": "Invalid format for '‹value›': expected ‹value›",
    "details": {}
  },
  "meta": {
    "timestamp": "2026-05-21T10:00:00Z",
    "request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
  }
}

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

Message

Invalid format for '‹value›': expected ‹value›
Formato no válido para '‹value›': se esperaba ‹value›
Format no vàlid per a '‹value›': s'esperava ‹value›

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