Dash0 · OAuth Scopes

Dash0 OAuth Scopes

OAuth 2.0 searched

Dash0 publishes 1 OAuth 2.0 scope via the authorizationCode and refreshToken flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Dash0 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.

ObservabilityOpenTelemetryMonitoringLogsMetricsTracingAPMPrometheusDevOpsCompanyApis

Scopes: 1 Flows: authorizationCode, refreshToken Method: searched

Scopes (1)

Scope	Description	Flows
*	Full-access wildcard scope. Dash0's OAuth Authorization Server Metadata advertises `scopes_supported: ["*"]` — a single wildcard scope rather than a granular per-resource scope catalog. Fine-grained access is instead governed by organization roles/RBAC and dataset scoping (the `dataset` query parameter), not by OAuth scopes.	authorizationCode

📄 Provider scope reference: https://api-docs.dash0.com/reference/get_well-known-oauth-authorization-server

Source

OAuth Scopes

generated: '2026-07-18'
method: searched
source: https://api.eu-west-1.aws.dash0.com/.well-known/oauth-authorization-server
docs: https://api-docs.dash0.com/reference/get_well-known-oauth-authorization-server
schemes:
- name: OAuth2
  authorizationUrl: https://api.<region>.aws.dash0.com/oauth/authorize
  tokenUrl: https://api.<region>.aws.dash0.com/oauth/token
  flows: [authorizationCode, refreshToken]
scopes:
- scope: '*'
  description: >-
    Full-access wildcard scope. Dash0's OAuth Authorization Server Metadata
    advertises `scopes_supported: ["*"]` — a single wildcard scope rather than a
    granular per-resource scope catalog. Fine-grained access is instead governed
    by organization roles/RBAC and dataset scoping (the `dataset` query
    parameter), not by OAuth scopes.
  flows: [authorizationCode]
notes: >-
  Bearer auth-token requests (the primary API auth) are not scoped via OAuth;
  they carry organization-level access. This artifact reflects the OAuth surface
  used by the CLI and MCP clients.