Scope missing

scope.missing · HTTP 403

What it means

Your API key or your role in the workspace lacks the scope this route needs; the problem's requiredScope field names it. On organisation routes, your organisation role is below the one the route needs, named in requiredRole.

What to do

A key's scopes are fixed when it is created: create a key with the scope on the dashboard's API keys page and revoke the old one. For a role, ask an Admin of the organisation to change it.

Every error the API returns is a JSON problem (RFC 9457) whose code names it and whose type links to its page here. See the docs for how the API works.