type URI on every not_found problem body: https://docs.get-exo.com/errors/not_found.
HTTP status: 404 Not Found.
Why it happens
This is the generic 404 the API falls back to when a route has no more specific code. Most families raise something narrower:node_not_found, job_not_found, export_not_found and so on.
Exo returns 404 rather than 403 for a resource that exists but belongs to someone else. That keeps ids unenumerable: a 403 would confirm the id is real.
How to fix it
- Confirm the id came from a list route on the same credential.
- If you are addressing another member’s resource, that is the expected answer. Resources are scoped to the caller, and a provisioned subject is reached with
X-Exo-Subjectrather than by guessing ids.
Related
node_not_foundjob_not_foundsubject_not_found- Errors for the envelope and the full catalogue