API · problem · HTTP 500
This request failed on our side
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
internal-error- When it happens
- Something this service depends on did not answer, or a handler has a fault. It is not a fault in your request, and it is not the deployment being unconfigured, which answers 503.
- What to do
- Retry. If it persists, say which endpoint and roughly when: the log carries what actually failed, and the response deliberately does not.
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 | This request failed on our side |
| status | 500 |
| 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
- 400Malformed request
- 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