Hubble Contacts · OAuth Scopes

Hubble Contacts OAuth Scopes

OAuth 2.0 searched

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

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

CompanyE-CommerceRetailHealthVision CareContact LensesSubscriptionsAgentic CommerceModel Context ProtocolShopifyGraphQL

Scopes: 4 Flows: authorizationCode Method: searched

OAuth endpoints

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

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

Flows
authorizationCode

Scopes (4)

Scope	Description	Flows
openid	OpenID Connect authentication; issues an ID token identifying the customer.	authorizationCode
email	Access to the customer's email address and email_verified claim.	authorizationCode
customer-account-api:full	Full access to the authenticated customer's account API — orders, subscriptions, addresses and profile.	authorizationCode
customer-account-mcp-api:full	Full access to the customer account surface over MCP, for agents acting on the authenticated customer's behalf.	authorizationCode

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

Source

OAuth Scopes

generated: '2026-08-04'
method: searched
source: https://account.hubblecontacts.com/.well-known/openid-configuration
docs: https://account.hubblecontacts.com/.well-known/oauth-authorization-server
notes: >-
  Scopes are read verbatim from the scopes_supported array of the OAuth/OIDC
  discovery documents Hubble's storefront host serves. There is no OpenAPI with
  oauth2 securitySchemes to derive from, and Hubble publishes no scope reference page
  of its own — the authorization server is the Shopify customer accounts issuer bound
  to Hubble's shop id. Descriptions below are the standard meanings of these scopes;
  no scope is listed that the discovery document does not name.
schemes:
- name: shopify-customer-accounts
  issuer: https://shopify.com/authentication/15165228
  source: well-known/hubble-contacts-openid-configuration.json
  flows:
  - flow: authorizationCode
    authorizationUrl: https://shopify.com/authentication/15165228/oauth/authorize
    tokenUrl: https://shopify.com/authentication/15165228/oauth/token
    pkce: S256
scopes:
- scope: openid
  description: OpenID Connect authentication; issues an ID token identifying the customer.
  flows: [authorizationCode]
  sources: [well-known/hubble-contacts-openid-configuration.json]
- scope: email
  description: Access to the customer's email address and email_verified claim.
  flows: [authorizationCode]
  sources: [well-known/hubble-contacts-openid-configuration.json]
- scope: 'customer-account-api:full'
  description: Full access to the authenticated customer's account API — orders, subscriptions, addresses and profile.
  flows: [authorizationCode]
  sources: [well-known/hubble-contacts-openid-configuration.json]
- scope: 'customer-account-mcp-api:full'
  description: Full access to the customer account surface over MCP, for agents acting on the authenticated customer's behalf.
  flows: [authorizationCode]
  sources: [well-known/hubble-contacts-openid-configuration.json]
x-evidence:
  fetched: '2026-08-04'
  url: https://account.hubblecontacts.com/.well-known/openid-configuration
  http_status: 200