unencodable_character

A field contains a character ISO-8859-1 cannot represent.

What to do

The message names the character, its code point and its position, and suggests a plain replacement for the ones an editor inserts on your behalf (curly quotes, en/em dashes, the ellipsis). A DTE is signed over its UTF-8 text and transmitted as ISO-8859-1 bytes, so such a character is sent as ? and the SII rejects the signature. Nothing was emitted and no folio was spent.

The envelope

{
  "error": {
    "type": "invalid_request_error",
    "code": "unencodable_character",
    "message": "…",
    "hint": "The message names the character, its code point and its position, and suggests a plain replacement for the ones an editor inserts on your behalf (curly quotes, en/em dashes, the ellipsis). A DTE is signed over its UTF-8 text and transmitted as ISO-8859-1 bytes, so such a character is sent as `?` and the SII rejects the signature. Nothing was emitted and no folio was spent.",
    "retriable": false,
    "doc_url": "https://docs.facturia.cl/errors/unencodable_character",
    "request_id": "req_01K2R7Q9M4T2VB"
  }
}

Program against code, never against message — the prose can be rewritten, the code cannot (§5.8).

hint and retriable arrive in the response with these exact values: they are a function of code and come from the same dictionary GET /v1/error_codes serves, so the envelope and the dictionary cannot disagree. Both are English on the wire by design — one registry, one language. More in The error envelope.

See also

The machine-readable copy of this page lives at GET /v1/error_codes, unauthenticated.