Anaconda · OAuth Scopes

Anaconda OAuth Scopes

OAuth 2.0 probed

Anaconda publishes 3 OAuth 2.0 scopes via the authorizationCode, clientCredentials, deviceCode, password, and refreshToken flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Anaconda API on a user’s behalf.

Tokens are issued from https://anaconda.com/api/auth/oauth2/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.

CompanyData ScienceMachine LearningArtificial IntelligencePackage ManagementPythonDeveloper ToolsSoftware Supply ChainRepositoryPackage RegistryCondaMCP

Scopes: 3 Flows: authorizationCode, clientCredentials, deviceCode, password, refreshToken Method: probed

OAuth endpoints

Authorization URL
https://anaconda.com/api/auth/oauth2/authorize

Token URL
https://anaconda.com/api/auth/oauth2/token

Flows
authorizationCodeclientCredentialsdeviceCodepasswordrefreshToken

Scopes (3)

Scope	Description	Flows
openid	Standard OIDC scope requesting an ID token.	authorizationCode, deviceCode
profile	Access to the authenticated user's basic profile claims.	authorizationCode, deviceCode
email	Access to the authenticated user's email address claim.	authorizationCode, deviceCode

📄 Provider scope reference: https://anaconda.com/docs/cli-reference/anaconda-auth/getting-started

Source

OAuth Scopes

generated: '2026-08-02'
method: probed
source: https://anaconda.com/.well-known/openid-configuration
docs: https://anaconda.com/docs/cli-reference/anaconda-auth/getting-started
note: No Anaconda OpenAPI declares an oauth2 securityScheme, so no scopes could be
  derived from the specifications (derive-oauth-scopes.py returned zero). The scope
  set below is what Anaconda's own OIDC discovery document advertises. The Anaconda
  Server repository API additionally exposes a runtime scope registry at `GET /system/scopes`
  (operationId repo.endpoints.system.scopes), but that endpoint requires authentication,
  so its contents are not enumerated here.
schemes:
- name: Anaconda OIDC
  type: openIdConnect
  issuer: https://auth.anaconda.com/api/auth
  discovery: https://anaconda.com/.well-known/openid-configuration
  source: well-known/anaconda-openid-configuration.json
  flows:
  - flow: authorizationCode
    authorizationUrl: https://anaconda.com/api/auth/oauth2/authorize
    tokenUrl: https://anaconda.com/api/auth/oauth2/token
  - flow: clientCredentials
    tokenUrl: https://anaconda.com/api/auth/oauth2/token
  - flow: deviceCode
    deviceAuthorizationUrl: https://anaconda.com/api/auth/oauth2/device/authorize
    tokenUrl: https://anaconda.com/api/auth/oauth2/token
  - flow: password
    tokenUrl: https://anaconda.com/api/auth/oauth2/token
  - flow: refreshToken
    tokenUrl: https://anaconda.com/api/auth/oauth2/token
scopes:
- scope: openid
  description: Standard OIDC scope requesting an ID token.
  flows: [authorizationCode, deviceCode]
  sources: [well-known/anaconda-openid-configuration.json]
- scope: profile
  description: Access to the authenticated user's basic profile claims.
  flows: [authorizationCode, deviceCode]
  sources: [well-known/anaconda-openid-configuration.json]
- scope: email
  description: Access to the authenticated user's email address claim.
  flows: [authorizationCode, deviceCode]
  sources: [well-known/anaconda-openid-configuration.json]
runtime_scope_registry:
  endpoint: GET /system/scopes
  api: anaconda:server-api
  operation_id: repo.endpoints.system.scopes
  summary: Get all possible scopes in system
  auth_required: true
  enumerated: false
x-evidence:
  fetched: '2026-08-02'
  http_status: 200