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
Flows
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.

📄 Provider scope reference:

Source

OAuth Scopes

Raw ↑ 
generated: '2026-07-18'
method: derived
source: openapi/conductorone-openapi-original.yml
schemes:
- name: oauth
  source: openapi/conductorone-openapi-original.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /auth/v1/token
  description: |-
    This API uses OAuth2 with the Client Credential flow.
    Client Credentials must be sent in the BODY, not the headers.
    For an example of how to implement this, refer to the [c1TokenSource.Token()](https://github.com/ConductorOne/conductorone-sdk-go/blob/3375fe7c0126d17e7ec4e711693dee7b791023aa/token_source.go#L101-L187) function.
scopes: []