Bugsnag · OAuth Scopes
Bugsnag OAuth Scopes
OAuth 2.0
probed
Bugsnag publishes 3 OAuth 2.0 scopes via the authorization_code and refresh_token flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Bugsnag API on a user’s behalf.
This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.
MonitoringObservabilityError MonitoringApplication Performance MonitoringDistributed TracingDeveloper ToolsSmartBear
Scopes: 3
Flows: authorization_code, refresh_token
Method: probed
Scopes (3)
| Scope | Description | Flows |
|---|---|---|
| api | Access to the BugSnag API on behalf of the authenticated user. Declared in scopes_supported; the provider publishes no per-resource breakdown of what it covers, so no finer decomposition is recorded here. | |
| openid | OpenID Connect sign-in scope, requesting an ID token. | |
| profile | Standard OIDC profile claims for the authenticated user. |
📄 Provider scope reference: https://developer.smartbear.com/smartbear-mcp/docs/remote-mcp-servers
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.