Eko Health · OAuth Scopes

Eko Health OAuth Scopes

OAuth 2.0 searched

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

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

CompanyHealthHealthcareMedical DevicesDigital HealthTelehealthArtificial IntelligenceCardiologyRemote Patient MonitoringCommerce

Scopes: 4 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://account.ekohealth.com/authentication/oauth/authorize

Token URL
https://account.ekohealth.com/authentication/oauth/token

Flows
authorizationCode

Scopes (4)

Scope	Description	Flows
openid	Standard OpenID Connect scope requesting an ID token for the signed-in customer.	authorizationCode
email	Release the customer's email address and email_verified claim.	authorizationCode
customer-account-api:full	Full access to the customer account API for the signed-in Eko Health customer.	authorizationCode
customer-account-mcp-api:full	Full access to the customer-account MCP API — the authenticated counterpart of the anonymous storefront MCP server at https://www.ekohealth.com/api/mcp.	authorizationCode

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-04'
method: searched
source: https://www.ekohealth.com/.well-known/openid-configuration
notes: >-
  Scopes taken verbatim from the scopes_supported array of the OAuth/OIDC discovery
  document Eko Health serves at www.ekohealth.com. These govern the storefront customer
  account and the customer-account MCP API. The Eko Connect API (api.ekodevices.com)
  publishes no scope surface — no OAuth metadata is served on that host — so it is not
  represented here. Descriptions below are the plain meaning of each scope name; Eko
  publishes no scope reference page.
schemes:
- name: shopify-customer-account-oidc
  source: well-known/eko-health-openid-configuration.json
  flows:
  - flow: authorizationCode
    authorizationUrl: https://account.ekohealth.com/authentication/oauth/authorize
    tokenUrl: https://account.ekohealth.com/authentication/oauth/token
    pkce: S256
scopes:
- scope: openid
  description: Standard OpenID Connect scope requesting an ID token for the signed-in customer.
  flows: [authorizationCode]
  sources: [well-known/eko-health-openid-configuration.json]
- scope: email
  description: Release the customer's email address and email_verified claim.
  flows: [authorizationCode]
  sources: [well-known/eko-health-openid-configuration.json]
- scope: 'customer-account-api:full'
  description: Full access to the customer account API for the signed-in Eko Health customer.
  flows: [authorizationCode]
  sources: [well-known/eko-health-openid-configuration.json]
- scope: 'customer-account-mcp-api:full'
  description: >-
    Full access to the customer-account MCP API — the authenticated counterpart of the
    anonymous storefront MCP server at https://www.ekohealth.com/api/mcp.
  flows: [authorizationCode]
  sources: [well-known/eko-health-openid-configuration.json]