Error reference

not_found

HTTP status

404 Not Found

Returned by

Every endpoint (request handling)

What it means

There is nothing at this address that the caller can see.

Typical causes

• A typo in the path, or a path that does not exist in /v1.
• The id is malformed or belongs to another type (a contact_… id where a lead_… id is expected).
• The record exists but the caller may not see it: Kweko answers 404 rather than 403 so ids of hidden records do not leak.
• The record belongs to another workspace.

How to fix it

• Check the path against the API reference and the id prefix.
• Check the key has the read scope for this record type.

Message

English text, as sent with Accept-Language: en. With ru or uz the API sends the translation.

• Not found.
  RU: Не найдено.
  UZ: Topilmadi.

Example response

HTTP/1.1 404 Not Found
Content-Type: application/json; charset=utf-8
X-Request-Id: req_4f2a9c1e0b7d3a55

{
  "error": {
    "code": "not_found",
    "message": "Not found.",
    "request_id": "req_4f2a9c1e0b7d3a55",
    "docs_url": "https://developers.kweko.uz/errors/not_found"
  }
}

Related

• gone
• invalid_id_type
• forbidden

All error codes · The error format