auth_org_mismatch
auth_org_mismatch
Section titled “auth_org_mismatch”HTTP status: 403 Forbidden
How to fix
Section titled “How to fix”- Confirm the resource ID belongs to YOUR org. Open the resource in the dashboard — if it loads, you're authenticated to the right org. If it doesn't show up at all, the ID is from a different org and we return this code rather than 404 because the resource type + ID pattern is recognizable.
- Check the active API key's org. Run
jc auth whoami(or hitGET /api/v1/account) — the response includes the org name and ID bound to the current credential. - Switch orgs in the dashboard via the org switcher in the top-left if you belong to multiple. The session and API keys are per-org.
- Regenerate the API key under the correct org if you're using a stale credential from a previous workspace.
What this means
Section titled “What this means”Your credential was valid but bound to org A, while the resource exists in org B. We return 403 here (not 404) only when the resource type + ID makes ownership unambiguous — otherwise the cross-org case returns not_found to prevent ID enumeration.
Related errors
Section titled “Related errors”not_found— cross-org case where existence would leakauth_forbidden— right org, wrong roleorg_not_found— the org itself is missing or inaccessible
Still stuck?
Section titled “Still stuck?”Contact support with your request_id (looks like req_01HF3JKB...). We'll confirm which org each side resolved to.