dispatch_not_applicable
`dispatch.transfer_type` or `dispatch.dispatch_type` was sent on a document type that carries no traslado.
dispatch.transfer_type or dispatch.dispatch_type was sent on a document type that carries no traslado.
| Code | dispatch_not_applicable |
| Type | unprocessable_error — Well formed, but breaks a domain rule |
| HTTP | 422 |
| Retriable? | No |
What to do
IndTraslado and TipoDespacho exist only on a guía de despacho (52). Drop the field, or emit a 52. The rest of the dispatch block is ignored on other tipos rather than refused, as it always has been.
Retrying the same request will fail the same way. Change the request, not the frequency.
The envelope
{
"error": {
"type": "unprocessable_error",
"code": "dispatch_not_applicable",
"message": "…",
"hint": "IndTraslado and TipoDespacho exist only on a guía de despacho (52). Drop the field, or emit a 52. The rest of the `dispatch` block is ignored on other tipos rather than refused, as it always has been.",
"retriable": false,
"doc_url": "https://docs.facturia.cl/errors/dispatch_not_applicable",
"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
Every code
The error envelope
The machine-readable copy of this page lives at GET /v1/error_codes, unauthenticated.