API · problem · HTTP 401
That path needs a key
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 refusalkey-required
- When it happens
- An account path was called with no credential. Unlike /v1, these have no open tier: they answer about one subscription and cannot do that without knowing which.
- What to do
- Send Authorization: Bearer <key>. Sign in at /account/ and the key is there: checkout returns you to that page, and the key is attached to the account rather than to a URL you have to keep.
The shape of the answerRFC 9457
Problem 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 | That path needs a key |
| status | 401 |
| detail | What went wrong, in this request. |
The full list of failures, with the schema, is in the API documentation.