unauthenticated
- HTTP status
- 401 Unauthorized
- Returned by
- API keys; Sign-in and authentication
What it means
Kweko could not accept the API key in the Authorization header.
Typical causes
- The key is mistyped, truncated or has extra characters (keys carry a checksum, so a single wrong character is caught).
- The key was sent to a workspace address (
<slug>.kweko.uz) of another workspace. A key belongs to exactly one workspace. - An API key was sent to a path outside
/v1: keys are accepted only on the public API.
How to fix it
- Copy the key again from Settings → Developers, or create a new one.
- Send requests to
https://api.kweko.uz/v1/….
Messages
English text, as sent with Accept-Language: en. With ru or uz the API sends the translation.
- API keys are accepted only on /v1 endpoints.
RU: API-ключи принимаются только на эндпоинтах /v1.
UZ: API kalitlar faqat /v1 endpointlarida qabul qilinadi. - Invalid API key.
RU: Неверный API-ключ.
UZ: API kalit notoʻgʻri. - This API key belongs to another workspace.
RU: Этот API-ключ принадлежит другому пространству.
UZ: Bu API kalit boshqa ish joyiga tegishli.
Example response
Response
HTTP/1.1 401 Unauthorized
Content-Type: application/json; charset=utf-8
X-Request-Id: req_4f2a9c1e0b7d3a55
{
"error": {
"code": "unauthenticated",
"message": "Invalid API key.",
"request_id": "req_4f2a9c1e0b7d3a55",
"docs_url": "https://developers.kweko.uz/errors/unauthenticated"
}
}