Octopus Deploy · OAuth Scopes
Octopus Deploy OAuth Scopes
OAuth 2.0
derived
Octopus Deploy 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 https://your-octopus-instance/api/oidc/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.
DevOpsContinuous DeliveryDeployment AutomationRelease ManagementRunbooksCI/CD
Scopes: 0
Flows: clientCredentials
Method: derived
OAuth endpoints
Token URL
https://your-octopus-instance/api/oidc/token
https://your-octopus-instance/api/oidc/token
Flows
clientCredentials
clientCredentials
Scopes (0)
Octopus Deploy 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.
Octopus Deploy does not use OAuth scopes; the OIDC client_credentials exchange only validates a service account identity, and API access is authorized by the service account's team and role permissions (or an API key) per https://octopus.com/docs/octopus-rest-api/openid-connect.
Octopus Deploy does not use OAuth scopes; the OIDC client_credentials exchange only validates a service account identity, and API access is authorized by the service account's team and role permissions (or an API key) per https://octopus.com/docs/octopus-rest-api/openid-connect.
📄 Provider scope reference: https://octopus.com/docs/octopus-rest-api/openid-connect