Poppi · OAuth Scopes
Poppi OAuth Scopes
OAuth 2.0
probed
Poppi 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.
CompanyConsumer Packaged GoodsBeveragesFood and BeverageE-CommerceDirect to ConsumerRetailAgentic CommerceShopifyMCP
Scopes: 0
Flows:
Method: probed
Scopes (0)
Poppi 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 read verbatim from scopes_supported in the store's OIDC discovery document. This is the Shopify Customer Accounts scope set for poppi's own authentication tenant (issuer https://shopify.com/authentication/22399731). poppi publishes no scope reference page of its own and the UCP MCP endpoint at /api/ucp/mcp is anonymous, so no scopes apply there.
Scopes are read verbatim from scopes_supported in the store's OIDC discovery document. This is the Shopify Customer Accounts scope set for poppi's own authentication tenant (issuer https://shopify.com/authentication/22399731). poppi publishes no scope reference page of its own and the UCP MCP endpoint at /api/ucp/mcp is anonymous, so no scopes apply there.
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.