Omaze · OAuth Scopes
Omaze OAuth Scopes
OAuth 2.0
probed
Omaze publishes 4 OAuth 2.0 scopes via the authorization_code flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Omaze 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.
CompanyCharityFundraisingNon-ProfitPrize DrawsSweepstakesE-CommerceAgentic CommerceUniversal Commerce ProtocolMCPShopifyUnited KingdomGermany
Scopes: 4
Flows: authorization_code
Method: probed
Scopes (4)
| Scope | Description | Flows |
|---|---|---|
| openid | Standard OpenID Connect scope. Requests an ID token identifying the authenticated Omaze customer. | |
| Standard OpenID Connect scope. Releases the `email` and `email_verified` claims for the authenticated customer. | ||
| customer-account-api:full | Full access to the Shopify Customer Account API on behalf of the signed-in customer — the account surface behind /account on the storefront (orders, entries, subscriptions, profile). | |
| customer-account-mcp-api:full | Full access to the authenticated Customer Account MCP surface. This is the agent-facing counterpart to `customer-account-api:full`, and is distinct from the anonymous UCP shopping MCP endpoint at /api/ucp/mcp. |
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.