Cube Planning · OAuth Scopes

Cube Planning OAuth Scopes

OAuth 2.0 searched

Cube Planning publishes 3 OAuth 2.0 scopes via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Cube Planning API on a user’s behalf.

Tokens are issued from https://api.cubesoftware.com/o/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.

CompanyFP&AFinancial PlanningFinanceBudgetingForecastingAnalyticsPlanning

Scopes: 3 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://portal.cubesoftware.com/o/authorize/

Token URL
https://api.cubesoftware.com/o/token/

Flows
authorizationCode

Scopes (3)

Scope	Description	Flows
read	Read access to Cube resources.	authorizationCode
write	Write access to Cube resources.	authorizationCode
introspection	Permission to introspect access tokens via the introspection endpoint.	authorizationCode

📄 Provider scope reference: https://api.cubesoftware.com/.well-known/oauth-authorization-server

Source

OAuth Scopes

generated: '2026-07-18'
method: searched
source: openapi/cube-planning-openapi-original.yml
docs: https://api.cubesoftware.com/.well-known/oauth-authorization-server
schemes:
- name: OAuth2
  source: openapi/cube-planning-openapi-original.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://portal.cubesoftware.com/o/authorize/
    tokenUrl: https://api.cubesoftware.com/o/token/
    introspectionUrl: https://api.cubesoftware.com/o/introspect/
    pkce: S256
    grant_types: [authorization_code, refresh_token]
  description: Standard Cube OAuth 2.0 flow (authorization code + PKCE). The OpenAPI
    security scheme declares no scopes; the scopes below are taken verbatim from Cube's
    RFC 8414 OAuth authorization-server metadata document.
# Scopes are NOT declared per-operation in the OpenAPI; they are published in Cube's
# /.well-known/oauth-authorization-server document (scopes_supported).
scopes:
- scope: read
  description: Read access to Cube resources.
  flows: [authorizationCode]
  sources: ['well-known/cube-planning-oauth-authorization-server.json']
- scope: write
  description: Write access to Cube resources.
  flows: [authorizationCode]
  sources: ['well-known/cube-planning-oauth-authorization-server.json']
- scope: introspection
  description: Permission to introspect access tokens via the introspection endpoint.
  flows: [authorizationCode]
  sources: ['well-known/cube-planning-oauth-authorization-server.json']