H1 · Authentication Profile

H1 Authentication

Authentication

H1 secures its APIs with http across 1 declared security scheme, as derived from its OpenAPI definitions.

HealthcareUnited StatesLife SciencesProvider DataHealthcare APIPrice TransparencyEligibilityNetwork IntelligenceDigital HealthPharma
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

BearerAuth http
scheme: bearer · in: header ()

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-24'
method: searched
source: openapi/ribbon-health-api-openapi.json
docs: https://ribbon.readme.io/docs/authentication
summary:
  types:
  - http
  scheme: bearer-api-key
  note: >-
    The H1 (Ribbon Health) API authenticates every request with a customer API
    key passed in the HTTP Bearer scheme - Authorization: Bearer {customer_token}.
    There is no OAuth 2.0 / OpenID Connect surface; keys are issued via the
    request-demo onboarding rather than self-serve. Keep the key server-side.
schemes:
- name: BearerAuth
  type: http
  scheme: bearer
  in: header
  header: Authorization
  format: Bearer {customer_token}
  sources:
  - openapi/ribbon-health-api-openapi.json