org_not_found
org_not_found
Section titled “org_not_found”HTTP status: 404 Not Found
How to fix
Section titled “How to fix”- Confirm the
X-Org-IDheader (when you set one explicitly). It must be a UUID belonging to an org you're a member of. Copy-paste from the dashboard rather than typing. - Run
jc auth whoami(orGET /api/v1/account) to see which org your current credential resolves to. If the answer surprises you, you're using the wrong API key. - Check the org wasn't deleted. Orgs can be deleted from Settings → Danger Zone; their IDs return 404 forever after.
- Switch active org in the dashboard via the top-left org switcher if you belong to multiple workspaces.
What this means
Section titled “What this means”The path resolved to a valid route and your credentials authenticated, but the org context attached to the request doesn't match any active organization you have access to. We return 404 (not 403) for unrecognized org IDs so callers can't enumerate other orgs.
Related errors
Section titled “Related errors”not_found— generic missing-resource caseauth_org_mismatch— credential bound to a different org than the resourceauth_forbidden— right org, insufficient role
Still stuck?
Section titled “Still stuck?”Contact support with your request_id (looks like req_01HF3JKB...). We'll confirm whether the org ID was ever active under your account.