Paigo · OAuth Scopes

Paigo OAuth Scopes

OAuth 2.0 derived

Paigo 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://auth.paigo.tech/oauth/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.

BillingUsage-Based BillingMeteringInvoicingPricingSaaSSubscriptionsDeveloper ToolsFinOps
Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://auth.paigo.tech/oauth/token
Flows
clientCredentials

Scopes (0)

Paigo 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.

Paigo uses an OAuth 2.0 client_credentials flow (token from https://auth.paigo.tech/oauth/token with client ID/secret from Settings > API) and does not document or use OAuth scopes (https://docs.paigo.tech/overview/getting-started-with-paigo).

📄 Provider scope reference: https://docs.paigo.tech/overview/getting-started-with-paigo

Source

OAuth Scopes

paigo-scopes.yml Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/paigo-paigo-api-openapi.yml
docs: https://docs.paigo.tech/overview/getting-started-with-paigo
note: Paigo uses an OAuth 2.0 client_credentials flow (token from https://auth.paigo.tech/oauth/token with client ID/secret from Settings > API) and does not document or use OAuth scopes (https://docs.paigo.tech/overview/getting-started-with-paigo).
schemes:
- name: bearer
  source: openapi/paigo-paigo-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.paigo.tech/oauth/token
  description: Use bearer token to authenticate `Bearer <your access token>`
scopes: []