Quickstart
Introduction
Pierflow is the connectivity layer for healthcare in Africa — distribution rails for insurance products, and a Records API that turns paper records into FHIR R4 data your EMR or HMS can import.
Who Pierflow is for#
You're probably here because you're building one of these:
| You are… | What Pierflow gives you |
|---|---|
| A fintech or super-app | Embedded HMO plans, savings, benefits |
| An HR or payroll platform | Group enrollment across multiple HMOs |
| A hospital or clinic | Verification, claims, FHIR record exchange |
| An EMR / HMS vendor | Records API — pull historical patient data as FHIR R4 bundles |
| A diagnostic lab | Verification, claims, archive digitisation |
| An HMO software vendor | Distribution rails + AI scoring layer |
| A government programme | Population data exchange + analytics |
Two environments#
You'll have two sets of API keys — one for each environment. Start in sandbox; move to production when you're ready.
| Environment | Use it for |
|---|---|
| Sandbox | Synthetic plans, mock HMO connectors, test card numbers. Safe to break things. |
| Production | Real HMOs, real members, real money. Unlocked after a short review. |
Your API keys#
Once provisioned, your keys appear in the Pierflow developer portal. All keys follow the pattern pf_{environment}_{type}_{random}.
Keep secrets out of front-end code
Anything starting with
pf_*_sk_ is a secret key. Treat it like a password. Use the public client_id in front-end builds.