Mason · OAuth Scopes
Mason OAuth Scopes
OAuth 2.0
none
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.
CompanyE-CommerceCommerceArtificial IntelligenceAgentsContent GenerationDiscountsPromotionsWebhookShopify
Scopes: 0
Flows: password
Method: none
OAuth endpoints
Token URL
token
token
Flows
password
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.
The OAuth2 security scheme(s) in the OpenAPI declare no scopes, and no security requirement references one.
The OAuth2 security scheme(s) in the OpenAPI declare no scopes, and no security requirement references one.
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.