HealthEx · Authentication Profile

Healthex Authentication

Authentication

HealthEx secures its APIs with http and oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).

CompanyHealthcareHealth RecordsFHIRPatient ConsentData SharingInteroperabilityTEFCAMCPAgents

Methods: http, oauth2 Schemes: 2 OAuth flows: authorizationCode API key in:

Security Schemes

organizationBearerJWT http

scheme: bearer

patientOAuth2 oauth2

· flows: authorizationCode

Source

Authentication Profile

generated: '2026-07-19'
method: searched
source: https://docs.healthex.io/authentication
docs: https://docs.healthex.io/authentication
summary:
  types: [http, oauth2]
  http_scheme: bearer
  bearer_format: JWT
  oauth2_flows: [authorizationCode]
  models:
    - organization-api-token
    - patient-oauth2
schemes:
  - name: organizationBearerJWT
    type: http
    scheme: bearer
    bearerFormat: JWT
    description: >-
      Organization API access. Admins mint an apiKey / apiSecret pair in the
      HealthEx web-app Admin panel, then exchange them at the token endpoint for
      a JWT that is sent as `Authorization: Bearer <JWT>`. Tokens are valid for
      24 hours. HealthEx notes that none of the currently supported organization
      APIs require additional permissions/scopes.
    token_endpoint: https://api.healthex.io/v1/auth/token
    token_request:
      method: POST
      content_type: application/json
      body: '{"apiKey": "...", "apiSecret": "..."}'
    token_lifetime_hours: 24
    sources: [docs.healthex.io/authentication]
  - name: patientOAuth2
    type: oauth2
    description: >-
      Patient-mediated OAuth 2.0 (SMART-on-FHIR style) for accessing an
      individual patient's consented FHIR records and the MCP server. PKCE
      (S256) required; public (none) and client_secret_post client auth
      supported.
    flows:
      - flow: authorizationCode
        authorizationUrl: https://api.healthex.io/oauth/authorize
        tokenUrl: https://api.healthex.io/oauth/token
        registrationUrl: https://api.healthex.io/oauth/register
        revocationUrl: https://api.healthex.io/oauth/revoke
        pkce: S256
        scopes:
          patient/*.read: Read access to the patient's consented FHIR records
          offline_access: Issue a refresh token for long-lived access
          openid: OpenID Connect authentication
          profile: Basic profile claims
          email: Email claim
    sources:
      - api.healthex.io/.well-known/oauth-authorization-server
      - api.healthex.io/.well-known/oauth-protected-resource

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact 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 security artifact

curl "https://apis.io/api/v1/security/healthex-authentication"

All security posture

curl "https://apis.io/api/v1/security?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.

GitHub Google LinkedIn

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