invalid_date
A date is not a real date in `YYYY-MM-DD` form.
A date is not a real date in YYYY-MM-DD form.
| Code | invalid_date |
| Type | invalid_request_error — Malformed or incomplete input |
| HTTP | 400 |
| Retriable? | No |
What to do
Civil dates are America/Santiago; timestamps are RFC 3339 UTC.
Retrying the same request will fail the same way. Change the request, not the frequency.
The envelope
{
"error": {
"type": "invalid_request_error",
"code": "invalid_date",
"message": "…",
"hint": "Civil dates are America/Santiago; timestamps are RFC 3339 UTC.",
"retriable": false,
"doc_url": "https://docs.facturia.cl/errors/invalid_date",
"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 full table, grouped by where you will run into it.
The error envelope
The nine types, the request_id and how to handle them in practice.
The machine-readable copy of this page lives at GET /v1/error_codes, unauthenticated.