Skip to main content

Scopes

Scopes define what an API key or OAuth bearer token can do. Session callers skip scope checks because the dashboard uses route-level organization and product authorization instead. Use the smallest scope set that can complete the workflow. Organization owners and admins can grant all catalog scopes; members can grant read scopes only. The key creation form pairs each selected write scope with its matching read scope. A scope does not make an internal endpoint public. Use the generated reference to find endpoints available to organization API keys. mcp:api is reserved for OAuth access tokens and cannot be granted to API keys.

Catalog

This catalog is copied from apps/client/src/lib/api/scopes.ts. Update both places whenever scopes are added, renamed, or removed.

Minimum scope examples

Denied requests

If a token-style caller lacks a required scope, TPC returns 403:
Create a new key or rotate the existing integration key from:
Do not add write scopes to a key used only for dashboards or reporting.