Poppy Handcrafted Popcorn · OAuth Scopes
Poppy Handcrafted Popcorn OAuth Scopes
OAuth 2.0
probed
Poppy Handcrafted Popcorn 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.
CompanyFood and BeverageConsumer Packaged GoodsRetailE-CommerceAgent CommerceUniversal Commerce ProtocolMCPShopifySnacks
Scopes: 0
Flows:
Method: probed
Scopes (0)
Poppy Handcrafted Popcorn 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.
derive-oauth-scopes.py found no oauth2 securitySchemes because there is no OpenAPI. These are the scopes_supported values the provider's own live OIDC discovery document advertises for its customer-account authorization server. Descriptions state the standard meaning of each scope; the provider publishes no scope reference page of its own.
derive-oauth-scopes.py found no oauth2 securitySchemes because there is no OpenAPI. These are the scopes_supported values the provider's own live OIDC discovery document advertises for its customer-account authorization server. Descriptions state the standard meaning of each scope; the provider publishes no scope reference page of its own.
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.