> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lasscyber.com/llms.txt
> Use this file to discover all available pages before exploring further.

# not_found

> HTTP 404 — resource does not exist or is not visible to this tenant.

|                 |                 |
| --------------- | --------------- |
| **HTTP status** | `404 Not Found` |
| **Code**        | `not_found`     |
| **Retry?**      | No.             |

## When this happens

The path is valid (the route exists) but the specific resource you
referenced does not exist — *or* exists in a different tenant and is
therefore invisible to your credential.

Common cases:

* A policy / rule / API key UUID that has been deleted.
* A policy slug that does not exist in your tenant.
* A path constructed from stale data (e.g. a deleted tenant ID).

## Example response

```json theme={null}
{
  "detail": "Policy not found.",
  "code": "not_found",
  "request_id": "5b3f6c7e-7d24-4d40-9b12-3a59c01c6e91",
  "doc_url": "https://docs.lasscyber.com/errors/not_found"
}
```

## Tenant isolation note

Agnes deliberately collapses cross-tenant lookups into 404s so the API
does not leak the existence of resources owned by other tenants. If
you are convinced the resource exists, double-check that you are
calling with the right tenant's API key.

## How to fix

1. Confirm the ID / slug you sent matches a real resource (list the
   collection or check the dashboard).
2. Confirm you are using a key from the owning tenant.
3. If a resource was deleted intentionally, update the caller to stop
   referencing it.

## SDK behaviour

| SDK        | Exception             |
| ---------- | --------------------- |
| Python     | `agnes.NotFoundError` |
| TypeScript | `NotFoundError`       |

SDKs do not retry 404s.

## Related

* [Pagination](/api-reference/pagination) — list a collection to
  confirm the ID exists.