insufficient_scope
HTTP 403 — Insufficient scope
insufficient_scope means the API key is valid but was not granted the permission (scope) this endpoint requires.
What it means
The key is valid but was not granted the scope this endpoint requires. The problem detail names the missing scope.
Common causes
- The key was created with a narrower scope selection than the request needs.
How to fix it
Create a new key that includes the required scope (keys are immutable once minted — scoping is a create-time decision), or call an endpoint the key's scopes cover.
Should you retry?
No — the grant does not change between attempts.
The response shape
Every /v1 error is an RFC 9457 application/problem+json document: type links to this page, code is the stable value to branch on (never parse title or detail), and request_id identifies the request to support. Validation failures add an errors array of per-field JSON pointers.
API overview · API reference · All error codes:
missing_credentials— HTTP 401, Missing credentialsinvalid_api_key— HTTP 401, Invalid API keyinvalid_token— HTTP 401, Invalid access tokenunsupported_credential_type— HTTP 403, Credential type not usable on this surfacefeature_not_enabled— HTTP 403, Feature not enabled on this planvalidation_failed— HTTP 400, Request validation failedresource_not_found— HTTP 404, Resource not foundrate_limited— HTTP 429, Rate limit exceededquota_exhausted— HTTP 429, Plan quota exhaustedidempotency_key_reused— HTTP 422, Idempotency-Key reused with a different requestidempotency_in_progress— HTTP 409, A request with this Idempotency-Key is still in progressinternal_error— HTTP 500, Internal server error