Errors
Resource not found
No such resource within the caller's tenancy. It is also the answer where confirming that something exists would itself leak: an expired invitation token and one that never existed are indistinguishable on purpose.
- Code
- NOT_FOUND
- HTTP status
- 404
- Type
- https://myna.sh/errors/not-found
What to do
Check the id or slug, and check that the credential's organization or project scope covers it. A resource in another tenant is not found rather than forbidden.
application/problem+json
{ "type": "https://myna.sh/errors/not-found", "title": "Resource not found", "status": 404, "code": "NOT_FOUND", "detail": "A human-readable explanation of this particular occurrence.", "requestId": "req_01k…" }
