API · problem · HTTP 400
Malformed request
This page is what the type field of the error points at. Every answer this API refuses carries one, and it is a stable address rather than a version of the docs.
The refusal
bad-request- When it happens
- A parameter is missing, blank, out of range, or not a value this endpoint accepts. A blank parameter is malformed rather than zero: ?units= means a field somebody meant to fill.
- What to do
- The detail names the parameter and, where the set is finite, lists what it accepts. Every enumeration in GET /v1/openapi.json is derived from the corpus, so it cannot be stale.
The shape of the answer
RFC 9457Problem details: type, title, status and detail, plus whatever the individual failure can usefully add. The detail is written for the person reading the log, and names the parameter or the id that caused it.
| type | This page’s address. Stable. |
|---|---|
| title | Malformed request |
| status | 400 |
| detail | What went wrong, in this request. |
The full list of failures, with the schema, is in the API documentation.
Every refusal this API can return
12 types- 404No such resource
- 402The open tier runs twelve months behind
- 404Nothing in force on that date
- 404There is no national figure
- 400That regime belongs to another domain
- 401That path needs a key
- 401That key is not valid
- 405That path does not answer this method
- 503Ceiling reached
- 503This deployment is not fully configured
- 500This request failed on our side