Scopes
Status: Current (Scale plan). Every/v1 endpoint requires a scope carried by your API key. A call whose key lacks the required scope returns 403 forbidden.
A newly minted key gets the default set below. The opt-in scopes must be requested explicitly at mint time. Webhooks and keys are opt-in because they are secret-bearing surfaces — a leaked default-scope key should not be able to reroute event deliveries or enumerate credentials.
A key minted before a scope existed does not gain it retroactively. Re-mint the key, or update its scopes, to pick up new surfaces.
Default scopes (9)
Present on every newly minted key.Opt-in scopes (4)
Secret-bearing. Request them explicitly at mint time.What a missing scope looks like
A call without the required scope returns the standard/v1 error envelope with code forbidden:
error.code, not on the message.
Next
- Authentication — obtain the session your scopes ride on.
- Runs · Schedules · Webhooks — the endpoint groups behind each scope.