API · problem · HTTP 503
This deployment is not fully configured
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
service-unconfigured- When it happens
- A deployment is missing one of the settings this service refuses to run without: its spend ceiling, its key store or its identity provider. Every path answers this, including /health, and the pages of the site keep serving.
- What to do
- Nothing on your side. Retry after the delay in Retry-After. The log names the setting; the response deliberately does not, because that would tell anyone who finds the URL how this service is configured.
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 deployment is not fully configured |
| status | 503 |
| 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
- 500This request failed on our side