auth_forbidden
auth_forbidden
Section titled “auth_forbidden”HTTP status: 403 Forbidden
How to fix
Section titled “How to fix”- Check your role in the org. Open Settings → Members in the dashboard. Each row shows a role; only Admins can mutate workflows, manage members, and rotate API keys.
- Request elevation from an org admin if the action is intentional. Admins can change your role from the same Members panel.
- If you're hitting an API key route, confirm the key wasn't created with a restricted scope. Scoped keys (when available) appear in Settings → API Keys with a non-empty scope column.
- For superadmin-only endpoints (
/api/v1/admin/*), only the platform team can call those — the surface isn't customer-accessible.
What this means
Section titled “What this means”The API gateway accepted your credentials and resolved them to a user, but the RBAC check rejected the action. This is distinct from auth_invalid (credentials wrong) and auth_missing (no credentials).
Related errors
Section titled “Related errors”auth_invalid— credentials wrong/expired/revokedauth_missing— no credentials sentauth_org_mismatch— authenticated to the wrong organization
Still stuck?
Section titled “Still stuck?”Contact support with your request_id (looks like req_01HF3JKB...). We'll surface which permission check fired.