Clarify Health · OAuth Scopes

Clarify Health OAuth Scopes

OAuth 2.0 probed

Clarify Health uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

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.

CompanyHealth TechHealthcare AnalyticsHealth DataOutcomesReferral IntelligencePayersLife Sciences
Scopes: 0 Flows: Method: probed

Scopes (0)

Clarify Health implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

Clarify Health publishes no scope or permission reference page — there is no developer portal to publish one on. These are the scopes the two live OIDC issuers advertise in their own discovery documents. They are ALL standard OpenID Connect / OAuth 2.0 identity scopes; not one Clarify-specific resource scope is advertised anywhere, which is the finding. A custom Okta authorization server may carry product scopes, but /oauth2/default/.well-known/openid-configuration returns 401 (E0000015) so they are not anonymously discoverable.

Source

OAuth Scopes

clarify-health-scopes.yml Raw ↑
generated: '2026-08-15'
method: probed
source: >-
  scopes_supported read verbatim from
  https://auth.clarifyhealth.com/.well-known/openid-configuration (200) and
  https://okta.clarifyhealth.com/.well-known/openid-configuration (200), fetched 2026-08-15
docs: null
note: >-
  Clarify Health publishes no scope or permission reference page — there is no developer
  portal to publish one on. These are the scopes the two live OIDC issuers advertise in
  their own discovery documents. They are ALL standard OpenID Connect / OAuth 2.0 identity
  scopes; not one Clarify-specific resource scope is advertised anywhere, which is the
  finding. A custom Okta authorization server may carry product scopes, but
  /oauth2/default/.well-known/openid-configuration returns 401 (E0000015) so they are not
  anonymously discoverable.
issuers:
- issuer: https://auth.clarifyhealth.com/
  platform: Auth0
  scope_count: 14
  scopes:
  - name: openid
    description: Request an ID token (OpenID Connect core).
    standard: true
  - name: profile
    description: Basic profile claims for the authenticated user.
    standard: true
  - name: offline_access
    description: Issue a refresh token.
    standard: true
  - name: name
    description: Full name claim.
    standard: true
  - name: given_name
    description: Given name claim.
    standard: true
  - name: family_name
    description: Family name claim.
    standard: true
  - name: nickname
    description: Nickname claim.
    standard: true
  - name: email
    description: Email address claim.
    standard: true
  - name: email_verified
    description: Email verification status claim.
    standard: true
  - name: picture
    description: Profile picture claim.
    standard: true
  - name: created_at
    description: Account creation timestamp claim (Auth0 extension).
    standard: false
  - name: identities
    description: Linked identity provider records (Auth0 extension).
    standard: false
  - name: phone
    description: Phone number claim.
    standard: true
  - name: address
    description: Address claim.
    standard: true
- issuer: https://okta.clarifyhealth.com
  platform: Okta
  scope_count: 7
  scopes:
  - name: openid
    description: Request an ID token (OpenID Connect core).
    standard: true
  - name: email
    description: Email address claim.
    standard: true
  - name: profile
    description: Basic profile claims.
    standard: true
  - name: address
    description: Address claim.
    standard: true
  - name: phone
    description: Phone number claim.
    standard: true
  - name: offline_access
    description: Issue a refresh token.
    standard: true
  - name: groups
    description: Group memberships of the authenticated user (Okta org server).
    standard: false
summary:
  total_scopes: 21
  resource_scopes: 0
  identity_scopes: 21

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this
  • find_scopesBrowse and filter every scope set in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This scope set
curl "https://apis.io/api/v1/scopes/clarify-health-scopes"
All oauth scopes
curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.