Alphaus · OAuth Scopes

Alphaus OAuth Scopes

OAuth 2.0 searched

Alphaus publishes 1 OAuth 2.0 scope. Scopes are the fine-grained permissions an application requests at authorization time to act against the Alphaus API on a user’s behalf.

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.

CompanyFinOpsCloud Cost ManagementCloudBillingMulti-CloudAzureGCPgRPCCost OptimizationReseller BillingAPI
Scopes: 1 Flows: Method: searched

Scopes (1)

ScopeDescriptionFlows
openid OpenID Connect scope requested in the client_credentials token exchange. Blue API documents scope=openid for the access-token request; fine-grained authorization beyond the token is enforced by the Iam service (RBAC roles/permissions), not by additional OAuth scopes. clientCredentials

📄 Provider scope reference: https://labs.alphaus.cloud/docs/blueapi/authentication/

Source

OAuth Scopes

Raw ↑ 
generated: '2026-07-17'
method: searched
source: https://labs.alphaus.cloud/docs/blueapi/authentication/
docs: https://labs.alphaus.cloud/docs/blueapi/authentication/
schemes:
  - name: OAuth2ClientCredentials
    flow: clientCredentials
    token_urls:
      - https://login.alphaus.cloud/ripple/access_token
      - https://login.alphaus.cloud/access_token
scopes:
  - scope: openid
    description: >-
      OpenID Connect scope requested in the client_credentials token exchange. Blue API documents
      scope=openid for the access-token request; fine-grained authorization beyond the token is
      enforced by the Iam service (RBAC roles/permissions), not by additional OAuth scopes.
    flows: [clientCredentials]
    sources: [https://labs.alphaus.cloud/docs/blueapi/authentication/]
note: >-
  Blue API uses OAuth2 client credentials with a single openid scope; authorization granularity is
  handled by RBAC (Iam service), not a published OAuth scope catalog.