Developers
Build on the health connectivity layer for Africa.
One API across HMOs, providers, pharmacies, and the platforms that serve them. AI-native — every endpoint returns validated, normalised, and scored data.
From request to production in five steps.
- 01
Request API access
Tell us what you are building. We provision sandbox keys within one business day.
- 02
Pull the SDK
Install @pierflow/node or hit the REST API directly. Auth is a single bearer token.
- 03
Make your first call
GET /v1/plans returns a list of HMO products ranked by value_score — AI inline.
- 04
Enroll a member
POST /v1/enrollments creates a policy. The response includes fraud_score and identity_confidence.
- 05
Go live
Switch your bearer token to the production environment. Same surface, same shapes.
One platform, every health-data workflow.
Embedded insurance
Sell HMO products inside your fintech, payroll, or super-app — with collection and reconciliation handled.
Provider directories
Look up hospitals, clinics, pharmacies with capabilities, geolocation, and accepted plans.
Clinical data exchange
Move FHIR-canonical records between providers, insurers, and care teams.
Benefits verification
Verify a member's coverage in milliseconds at point of care.
Paper-to-FHIR migration
Pull historical paper patient records into your EMR or HMS as validated FHIR R4 bundles through the Records API.
Build on the health data layer.
The API is AI-native. Every endpoint returns data that has been validated, normalised, and scored. Not raw data from a system you need to clean yourself.
import Pierflow from '@pierflow/node';
const pf = new Pierflow({ apiKey: process.env.PIERFLOW_KEY });
const quote = await pf.quotes.create({
budget_ngn: 120000,
audience: 'individual'
});
// → { plans: [...], value_score, plan_match_score }