Mason · OAuth Scopes

Mason OAuth Scopes

OAuth 2.0 derived

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

CompanyEcommerceCommerceAIAgentsContent GenerationDiscountsPromotionsWebhooksShopify
Scopes: 0 Flows: password Method: derived

OAuth endpoints

Token URL
token
Flows
password

Scopes (0)

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

📄 Provider scope reference:

Source

OAuth Scopes

Raw ↑ 
generated: '2026-07-20'
method: derived
source: openapi/mason-apps-openapi.json, openapi/mason-generation-openapi.json, openapi/mason-search-openapi.json,
  openapi/mason-webhooks-openapi.json
schemes:
- name: OAuth2PasswordBearer
  source: openapi/mason-apps-openapi.json
  flows:
  - flow: password
    tokenUrl: token
- name: OAuth2PasswordBearer
  source: openapi/mason-generation-openapi.json
  flows:
  - flow: password
    tokenUrl: token
- name: OAuth2PasswordBearer
  source: openapi/mason-search-openapi.json
  flows:
  - flow: password
    tokenUrl: token
- name: OAuth2PasswordBearer
  source: openapi/mason-webhooks-openapi.json
  flows:
  - flow: password
    tokenUrl: token
scopes: []