UrbanStems · OAuth Scopes
UrbanStems OAuth Scopes
OAuth 2.0
probed
UrbanStems publishes 4 OAuth 2.0 scopes. Scopes are the fine-grained permissions an application requests at authorization time to act against the UrbanStems API on a user’s behalf.
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.
CompanyCommerceE-CommerceRetailFlowersGiftingAgentic CommerceUniversal Commerce ProtocolMCPShopifyDirect to Consumer
Scopes: 4
Flows:
Method: probed
Scopes (4)
| Scope | Description | Flows |
|---|---|---|
| openid | Request an ID token identifying the signed-in customer. | |
| Release the email and email_verified claims for the signed-in customer. | ||
| customer-account-api:full | Full access to the customer account surface on behalf of the signed-in customer — orders, addresses, profile and subscription state for this shop. | |
| customer-account-mcp-api:full | Full access to the customer-account MCP surface on behalf of the signed-in customer. This is the authenticated companion to the anonymous commerce MCP endpoint; it is the scope an agent would hold to act on a specific buyer's account rather than on the public catalog. |
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.