Error codes
resource.not_found
The path matched no route or the requested entity does not exist (or is not visible to this principal).
resource.not_found is returned at HTTP 404.
When this fires
Spring's NoResourceFoundException, plus the dashboard BFF's catch-all 404 when proxying to a v1 path that does not exist. Resources hidden by RLS appear identical to non-existent resources — this is intentional, so the response code does not leak whether a resource exists in another org.
What to do
Confirm the URL matches the OpenAPI spec, and that the resource id you are addressing belongs to the principal's organisation. If you can see the resource in the dashboard but the API returns 404, check whether your API key was minted in a different org.
See also
- SDK reference — the Python and TypeScript SDKs raise typed exceptions for codes in this namespace.
- Error code index — every code the runtime can return.