Octopus Deploy · OAuth Scopes
Octopus Deploy OAuth Scopes
OAuth 2.0
derived
Octopus Deploy publishes 1 OAuth 2.0 scope via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Octopus Deploy API on a user’s behalf.
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/CDDeveloper ToolsAustralia
Scopes: 1
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 (1)
| Scope | Description | Flows |
|---|---|---|
| none | Octopus Deploy does not define OAuth scopes; access is controlled via service account permissions. |
📄 Provider scope reference: https://octopus.com/docs/octopus-rest-api/openid-connect
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.