# resource_not_found

No resource with that ID exists in this workspace. What causes the BioFlow API's resource_not_found error (HTTP 404) and how to fix it.

HTTP 404 · `application/problem+json` · No resource with that ID exists in this workspace.

## What causes it

- The ID in the URL does not exist, was deleted, or belongs to a different workspace than the key's.

## How to fix it

- List the collection first (e.g. `GET /v1/pages`) and use the returned `id` values verbatim — IDs are opaque.
- Check the key belongs to the workspace that owns the resource.

## Example response body

```json
{
  "type": "https://getbioflow.com/docs/api/errors/resource-not-found",
  "title": "No resource with that ID exists in this workspace",
  "status": 404,
  "instance": "urn:request:req_01abc",
  "code": "resource_not_found",
  "request_id": "req_01abc"
}
```

Branch on the stable `code` field — `title` and `detail` are for humans and may
change. `type` (`https://getbioflow.com/docs/api/errors/resource-not-found`) always resolves to this page. Quote
`request_id` when contacting support. Full code registry on the
[API docs hub](/docs/api#errors); the complete surface is in the
[interactive reference](/docs/api-reference).