# resource-not-found

<Badge variant="warning">404 Not Found</Badge> <Badge variant="muted">resource-not-found</Badge>

| Field | Value |
|---|---|
| **Type URI** | `https://docs.kordiam.app/docs/errors/resource-not-found` |
| **HTTP Status** | `404 Not Found` |

## Description

The endpoint exists, but the requested resource does not exist, was deleted, or is not visible to the current caller.

## Response Example

```json
{
  "type": "https://docs.kordiam.app/docs/errors/resource-not-found",
  "title": "Resource Not Found",
  "status": 404,
  "detail": "The requested resource was not found",
  "instance": "/api/v2/elements/9999",
  "traceId": "abc-123-def"
}
```

## Common Causes

- Using an invalid or non-existent resource ID
- Attempting to access a resource that has been deleted
- Attempting to access a resource outside the caller's organization or permissions

## How to Fix

Verify the resource ID through a list or search endpoint and confirm the caller has access to the resource.