Hi Health · Authentication Profile

Hi Health Authentication

Authentication

Hi Health secures its APIs with oauth2 across 1 declared security scheme, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).

CompanyHealthInsurancePaymentsFintechCard IssuingReimbursementInsurTechDigital HealthSpeedinvest
Methods: oauth2 Schemes: 1 OAuth flows: clientCredentials API key in:

Security Schemes

OAuth2ClientCredentials oauth2

Source

Authentication Profile

hi-health-authentication.yml Raw ↑ 
generated: '2026-07-19'
method: searched
source: https://customer-api.getpliant.com/docs/authenticated-api-usage
note: >-
  Derived from the Pliant Pro API (Customer) authentication docs — the API powering hi.health by
  Pliant. No public OpenAPI is downloadable from the ReadMe-hosted portal, so this profile is
  captured from the published auth documentation rather than a machine-derived securityScheme.
summary:
  types: [oauth2]
  oauth2_flows: [clientCredentials]
  token_transport: bearer
  backend_only: true
  https_required: true
schemes:
- name: OAuth2ClientCredentials
  type: oauth2
  flow: clientCredentials
  provider: Auth0
  token_transport: Bearer token in Authorization header
  token_ttl_seconds: 86400
  environments:
  - env: production
    token_url: https://infinnityprodinternal.eu.auth0.com/oauth/token
    audience: api.getpliant.com/api/integration
    api_base: https://partner-api.getpliant.com/api/
  - env: sandbox
    token_url: https://infinnitystaginginternal.eu.auth0.com/oauth/token
    audience: api.staging.infinnitytest.com/api/integration
    api_base: https://sandbox.partner-api.getpliant.com/api/
  quota:
    headers: [Auth0-Client-Quota-Limit]
    exceeded_status: 429
notes:
- The authorization flow must be handled exclusively by a secure backend.
- All communication requires HTTPS; plain HTTP is unsupported.
- PCI-DSS certified sensitive-card-data endpoints use a dedicated host pci-api.getpliant.com.