`scope_missing`

HTTP	When
403	The token authenticates correctly but lacks the required scope.

The details.required field on the error envelope (when present) lists the scopes the endpoint accepts; if the token has any one of them the request will succeed. For example, GET /v1/notes requires notes:read. A key with only posts:read returns:

{
  "error": {
    "code": "scope_missing",
    "message": "Token lacks the required scope. Need one of: notes:read.",
    "request_id": "req_…",
    "docs_url": "https://docs.scripe.io/api/v1/errors#scope_missing"
  }
}

To recover, edit the key in Settings → Developer → API keys and tick the missing scope. Edits take effect within 5 seconds (we bust the auth cache on save). See auth.md §1.2 for the scope catalogue.

Spend cap exceeded Plan not eligible

Getting started

Resources

Errors

Scope missing

`scope_missing`

​scope_missing

`scope_missing`