Cascades Docs
Sign in to run requests with your own sandbox key. Sign in
View as Markdown Open in Claude Open in ChatGPT Add MCP server OpenAPI JSON OpenAPI YAML
403 Forbidden

insufficient_scope — Insufficient scope

Message “This token does not have the required scope.”

What causes it

  • The token authenticated, but its scope list does not include every scope the operation requires; `details[].message` lists the missing scopes (for example `executions:write`).
  • A read token is being used for a write operation, or an `executions:read` token is downloading artifacts or exports that need `executions:read:full`.

How to fix it

  1. Use a key issued with the scopes listed in `details`. Keys minted from the API & MCP page carry the full default set.
  2. Check scope before probing IDs — scope is enforced before the record lookup, so a 403 here says nothing about whether the resource exists.

Operations that return it

Any operation can return this code.

See the API reference for the full list of operations.

Example response

HTTP/1.1 403 Forbidden · Content-Type: application/json

403 Forbidden
{
  "error": {
    "code": "insufficient_scope",
    "message": "This token does not have the required scope.",
    "details": [
      {
        "field": "scope",
        "message": "executions:write"
      }
    ],
    "request_id": "6f1c2a3e-8d4b-4c5e-9f0a-1b2c3d4e5f60",
    "doc_url": "https://cascades.crscreditapi.com/docs/api/errors/insufficient_scope"
  }
}