Problem code
credential_in_url
| Status | 400 Bad Request |
| Type | https://api.librarika.dev.raynux.com/problems/credential_in_url |
| Title | Credential in url |
| Retry | With a new key, sent in the Authorization header. |
What it means
A credential was sent in the URL's query string. URLs end up in logs, so the key is treated as leaked and revoked at once, and the library's administrators are told.
What to do
Ask the library for a new key, and send credentials only in the Authorization header.
Example
HTTP/1.1 400 Bad Request
Content-Type: application/problem+json
X-Request-ID: 01JD8Q3W6Y2N5K7M9P0R4S6T8V
{
"type": "https://api.librarika.dev.raynux.com/problems/credential_in_url",
"title": "Credential in url",
"status": 400,
"code": "credential_in_url",
"detail": "Credentials must never be sent in the URL. The key is treated as leaked and is revoked.",
"request_id": "01JD8Q3W6Y2N5K7M9P0R4S6T8V"
}
The type URI https://api.librarika.dev.raynux.com/problems/credential_in_url is this page. The detail above is an example of the English text; it is translated into the request's language and may change, so match on code, never on detail.