Atolls · OAuth Scopes
Atolls OAuth Scopes
OAuth 2.0
probed
Atolls 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.
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.
CompanyConsumerE-CommerceAffiliate MarketingCashbackCouponsShoppingRetailIdentityOpenID Connect
Scopes: 0
Flows:
Method: probed
Scopes (0)
Atolls 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.
Scopes are taken verbatim from the `scopes_supported` array of the published OIDC discovery documents on the Pepper community hosts. There is no OpenAPI with oauth2 securitySchemes to derive from, and Atolls publishes no scopes/permissions reference page, so descriptions below are the standard OpenID Connect Core 1.0 definitions — marked as such — not text Atolls wrote.
Scopes are taken verbatim from the `scopes_supported` array of the published OIDC discovery documents on the Pepper community hosts. There is no OpenAPI with oauth2 securitySchemes to derive from, and Atolls publishes no scopes/permissions reference page, so descriptions below are the standard OpenID Connect Core 1.0 definitions — marked as such — not text Atolls wrote.