Skip to main content
An insurer connects to Heyrafiki through versioned payer observations and explicit workflow decisions. The insurer remains authoritative for membership, Benefit design, adjudication policy and payment advice. Heyrafiki records the bounded operational evidence that connects those decisions to delivered Care.

Coverage

Version payer observations without silently replacing their source history.

Claims

Submit delivered Care, request evidence and record line decisions.

Controls

Review amount identities, authority boundaries and reconciliation rules.
Start the pilot with one Benefit product, one service family and one synthetic cohort. Prove authority, retry safety, line arithmetic and reconciliation before expanding the mapping.

Integration architecture

The payer controls membership, Benefit design and adjudication policy. Heyrafiki controls the workflow contract, authorization boundary, retry behavior and audit evidence. The Practitioner controls the clinical record. A payment source supplies settlement evidence independently from payer advice.

End-to-end flow

1

Establish the authority mapping

Map one payer tenant to one Heyrafiki Organization and issue a separate project for each environment. Grant only the scopes required by the integration.
2

Load Coverage

Send individual observations through POST /coverages, or batches of up to 500 records through POST /coverage_batches. Each observation carries its source contract, source version, effective period and evidence references.
3

Check the Benefit

Call POST /eligibility_checks for the service date and requested amount. Treat ineligible as a decision with reason codes, not as a transport failure.
4

Reserve authorization when required

Create a pre-authorization from the eligibility decision and covered Booking. The payer records the decision through POST /preauthorizations/{preauthorization_id}/decisions.
5

Submit delivered Care

Create the Claim only after the covered Session is delivered. Send service codes, units, amounts and evidence references. Clinical Notes and private Conversation content do not enter this contract.
6

Adjudicate every line

Request bounded evidence when necessary, then record a versioned policy reference, line amounts and coded reasons through POST /claims/{claim_id}/adjudications.
7

Reconcile payer advice

Send remittance advice with allocations to Claims. Heyrafiki keeps advice separate from independent settlement evidence so an advice file cannot assert that money moved.

Record the first Coverage observation

The same request shape works across supported HTTP clients. Amounts are integers in the currency’s minor unit.

201 · Coverage observation

Repeating the same payload with the same idempotency key returns the original observation with 200. Reusing that key with different content returns 409 and writes no second observation.

Source data contract

Control ownership

Retry and recovery rules

  • Send an Idempotency-Key on every supported write.
  • Retry 429 and retryable 503 responses only after the stated delay.
  • Treat a timeout after submission as unknown. Retry with the same idempotency key.
  • Treat 409 as a state or idempotency conflict that requires review.
  • Persist the X-Request-Id with the payer’s integration log.
  • Consume Webhooks idempotently using the stable event identifier.

Data boundary

Payer APIs use opaque Member and evidence references. They exclude names, contacts, Diagnoses, Clinical Notes, Session content, Messages, Journal text and Assessment answers. Organization and project boundaries are enforced before resource access and again at the workflow capability.

Integration entry point

Use the OpenAPI 3.1 contract, Sandbox and acceptance test plan for technical due diligence. Request Sandbox access when your integration team is ready to test.
Last modified on August 10, 2026