ConductorOne · Authentication Profile

Conductorone Authentication

Authentication

ConductorOne secures its APIs with http and oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).

CompanyCloud SaasIdentity SecurityAccess GovernanceIdentity and Access ManagementAccess ReviewsProvisioningLeast PrivilegeMCP GovernanceSecurity
Methods: http, oauth2 Schemes: 2 OAuth flows: clientCredentials API key in:

Security Schemes

bearerAuth http
scheme: bearer
oauth oauth2
· flows: clientCredentials

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-18'
method: derived
source: openapi/conductorone-openapi-original.yml
summary:
  types:
  - http
  - oauth2
  oauth2_flows:
  - clientCredentials
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  sources:
  - openapi/conductorone-openapi-original.yml
- name: oauth
  type: oauth2
  flows:
  - flow: clientCredentials
    tokenUrl: /auth/v1/token
    scopes: 0
  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.
  sources:
  - openapi/conductorone-openapi-original.yml