# `NOT_FOUND` (HTTP 404): no such record on this account

The bulk job, monitor or suppression entry named in the path does not exist, or belongs to another account. Nothing is charged.

Records are looked up inside the calling account, so an id that belongs to somebody else answers exactly as an id that never existed. That is deliberate: telling the difference would confirm that another account holds that id.

A bulk job whose results were pruned answers this too. Result files are kept for the retention window published on the endpoint's reference page and removed with the job afterwards.

The same code answers a path that matches no endpoint at all, which is usually a typo or a stale base URL.

**What to do.** Check the id against the one the creating call returned, and that the key belongs to the same account. For a run created some time ago, download the results before the retention window closes.

```json
{
    "success": false,
    "error": {
        "code": "NOT_FOUND",
        "message": "No record with that id on this account.",
        "request_id": "req_01m1kgdm4xngzmbmff68g94w0c"
    }
}
```

Reference: https://spaw.co/docs/errors/NOT_FOUND