Bombas · OAuth Scopes

Bombas OAuth Scopes

OAuth 2.0 probed

Bombas 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 Bombas API on a user’s behalf.

Tokens are issued from https://shopify.com/authentication/11195850/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.

CompanyRetailEcommerceApparelDirect to ConsumerCommerceAgentic CommerceUniversal Commerce ProtocolModel Context ProtocolShopify

Scopes: 4 Flows: authorizationCode Method: probed

OAuth endpoints

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

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

Flows
authorizationCode

Scopes (4)

Scope	Description	Flows
openid	Standard OpenID Connect scope; requests an ID token identifying the signed-in Bombas customer.	authorizationCode
email	Releases the customer's email and email_verified claims.	authorizationCode
customer-account-api:full	Full access to the Shopify Customer Account API for the signed-in customer (orders, addresses, profile, subscriptions).	authorizationCode
customer-account-mcp-api:full	Full access to the Shopify customer-account MCP API for the signed-in customer - the authenticated, customer-scoped MCP surface, distinct from the anonymous UCP shopping MCP endpoint.	authorizationCode

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

Source

OAuth Scopes

generated: '2026-07-31'
method: probed
source: https://shop.bombas.com/.well-known/openid-configuration
docs: https://shop.bombas.com/.well-known/oauth-authorization-server
note: >-
  Bombas ships no OpenAPI, so these scopes were not derived from a spec. They
  are the scopes_supported list published verbatim by the Shopify customer
  account authorization server that fronts the Bombas storefront
  (issuer https://shopify.com/authentication/11195850). The UCP / MCP commerce
  endpoint at /api/ucp/mcp does not use these scopes - it authenticates the
  calling platform with a UCP-Agent profile URI instead - so this scope set
  covers customer-account access only.
schemes:
- name: shopify-customer-account-oidc
  source: well-known/bombas-openid-configuration.json
  issuer: https://shopify.com/authentication/11195850
  flows:
  - flow: authorizationCode
    authorizationUrl: https://shopify.com/authentication/11195850/oauth/authorize
    tokenUrl: https://shopify.com/authentication/11195850/oauth/token
    pkce: S256
scopes:
- scope: openid
  description: Standard OpenID Connect scope; requests an ID token identifying the
    signed-in Bombas customer.
  flows: [authorizationCode]
  sources: [well-known/bombas-openid-configuration.json]
- scope: email
  description: Releases the customer's email and email_verified claims.
  flows: [authorizationCode]
  sources: [well-known/bombas-openid-configuration.json]
- scope: customer-account-api:full
  description: Full access to the Shopify Customer Account API for the signed-in customer
    (orders, addresses, profile, subscriptions).
  flows: [authorizationCode]
  sources: [well-known/bombas-openid-configuration.json]
- scope: customer-account-mcp-api:full
  description: Full access to the Shopify customer-account MCP API for the signed-in
    customer - the authenticated, customer-scoped MCP surface, distinct from the
    anonymous UCP shopping MCP endpoint.
  flows: [authorizationCode]
  sources: [well-known/bombas-openid-configuration.json]
x-evidence:
  fetched: '2026-07-31'
  url: https://shop.bombas.com/.well-known/openid-configuration
  http_status: 200
  content_type: application/json