file_required

The multipart body carried no file part.

What to do

Name the part file. A part under another name is not read, because guessing which upload was meant is how the wrong document gets stored.

The envelope

{
  "error": {
    "type": "invalid_request_error",
    "code": "file_required",
    "message": "…",
    "hint": "Name the part `file`. A part under another name is not read, because guessing which upload was meant is how the wrong document gets stored.",
    "retriable": false,
    "doc_url": "https://docs.facturia.cl/errors/file_required",
    "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.