ConductorOne · OAuth Scopes
ConductorOne OAuth Scopes
OAuth 2.0
derived
ConductorOne uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.
Tokens are issued from /auth/v1/token.
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.
CompanyCloud SaasIdentity SecurityAccess GovernanceIdentity and Access ManagementAccess ReviewsProvisioningLeast PrivilegeMCP GovernanceSecurity
Scopes: 0
Flows: clientCredentials
Method: derived
OAuth endpoints
Token URL
/auth/v1/token
/auth/v1/token
Flows
clientCredentials
clientCredentials
Scopes (0)
ConductorOne implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.
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.