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

# Subject not found

> The subject named in the request body does not exist in this organization.

This page is the resolution target of the RFC 9457 `type` URI on every `subject_not_found` problem body: `https://docs.get-exo.com/errors/subject_not_found`.

**HTTP status: `404` Not Found**.

```json theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
{
  "type": "https://docs.get-exo.com/errors/subject_not_found",
  "title": "Subject not found",
  "status": 404,
  "detail": "The subject is not provisioned.",
  "code": "subject_not_found",
  "requestId": "req_9f2c41ab7d0e5c18"
}
```

## Why it happens

This is the purge family's answer for a `subjectId` that names nothing. Unlike `subject_not_provisioned`, which comes from the subject seam and concerns the selector header, this concerns a subject named as the object of the call.

## How to fix it

* List provisioned subjects with `GET /v1/subjects` and use an id from there.
* If the subject was already erased, there is nothing left to purge and no action is needed.

## Related

* [`subject_not_provisioned`](/errors/subject_not_provisioned)
* [`subject_mapping_invalid`](/errors/subject_mapping_invalid)
* [Errors](/platform/errors) for the envelope and the full catalogue