ColdSnap · OAuth Scopes

ColdSnap OAuth Scopes

OAuth 2.0 searched

ColdSnap publishes 4 OAuth 2.0 scopes via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the ColdSnap API on a user’s behalf.

Tokens are issued from https://shopify.com/authentication/97378959650/oauth/token.

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-CommerceRetailFood and BeverageConsumer ProductsHardwareAppliancesFoodserviceAgentic CommerceShopifyGraphQLModel Context ProtocolUniversal Commerce Protocol

Scopes: 4 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://shopify.com/authentication/97378959650/oauth/authorize

Token URL
https://shopify.com/authentication/97378959650/oauth/token

Flows
authorizationCode

Scopes (4)

Scope	Description	Flows
openid	Request an OpenID Connect id_token identifying the customer.	authorizationCode
email	Release the customer's email address and email_verified claim.	authorizationCode
customer-account-api:full	Full access to the Shopify Customer Account API on behalf of the signed-in customer - orders, addresses, profile and subscription state for this store.	authorizationCode
customer-account-mcp-api:full	Full access to the customer-account MCP surface on behalf of the signed-in customer. This is the authenticated agent scope; the anonymous storefront MCP server at /api/mcp requires no scope at all.	authorizationCode

📄 Provider scope reference: https://coldsnap.com/.well-known/oauth-authorization-server

Source

OAuth Scopes

generated: '2026-08-02'
method: searched
source: https://coldsnap.com/.well-known/openid-configuration
docs: https://coldsnap.com/.well-known/oauth-authorization-server
note: >-
  Scopes were read from the live OpenID Connect / RFC 8414 discovery documents served
  at the ColdSnap origin, not from an OpenAPI oauth2 securityScheme - ColdSnap publishes
  no OpenAPI.
schemes:
- name: shopify-customer-accounts
  issuer: https://shopify.com/authentication/97378959650
  source: https://coldsnap.com/.well-known/openid-configuration
  flows:
  - flow: authorizationCode
    authorizationUrl: https://shopify.com/authentication/97378959650/oauth/authorize
    tokenUrl: https://shopify.com/authentication/97378959650/oauth/token
    code_challenge_methods: [S256]
scopes:
- scope: openid
  description: Request an OpenID Connect id_token identifying the customer.
  flows: [authorizationCode]
  sources: ['https://coldsnap.com/.well-known/openid-configuration']
- scope: email
  description: Release the customer's email address and email_verified claim.
  flows: [authorizationCode]
  sources: ['https://coldsnap.com/.well-known/openid-configuration']
- scope: customer-account-api:full
  description: >-
    Full access to the Shopify Customer Account API on behalf of the signed-in customer -
    orders, addresses, profile and subscription state for this store.
  flows: [authorizationCode]
  sources: ['https://coldsnap.com/.well-known/openid-configuration']
- scope: customer-account-mcp-api:full
  description: >-
    Full access to the customer-account MCP surface on behalf of the signed-in customer.
    This is the authenticated agent scope; the anonymous storefront MCP server at
    /api/mcp requires no scope at all.
  flows: [authorizationCode]
  sources: ['https://coldsnap.com/.well-known/openid-configuration']
observed_in_the_wild:
- scope_set: 'openid email customer-account-api'
  where: >-
    the authorize redirect emitted by https://coldsnap.com/customer_authentication/login
  note: the storefront's own login flow requests the narrower customer-account scope,
    not the :full variant advertised in discovery.
x-evidence:
  fetched: '2026-08-02'
  url: https://coldsnap.com/.well-known/openid-configuration
  http_status: 200