One integration. Multiple healthcare capabilities.
REST, scoped keys, signed webhooks, a real-time stream, and two SDKs. Below, the API surface as it actually is — including the parts you cannot call yet.
What you can call today.
One of these four has endpoints. The other three have a badge and a date we will not invent.
- Available
Financial services
Collection, payouts, wallets and an immutable double-entry ledger through one API. Money movement is executed by licensed payment institutions and mobile money operators — AZ54 never holds funds.
In production today.
Executed by licensed payment institutions and mobile money operators
- In development
Digital screening
Camera-based screening that turns devices staff already own into first-line risk identification tools. Deployed in the field today; programmatic access is in development.
Being built. Not available to integrate today.
- In development
Patient engagement
Reminders, follow-up and referral messaging that extend care beyond the point of interaction. In development — there is no public API for it today.
Being built. Not available to integrate today.
- Roadmap
Health data & analytics
Cross-network intelligence built on routine dispensing data: availability, price movement, stock-out risk, screening coverage. On the roadmap. Transaction-level reporting, on the other hand, is available today.
Planned. Design and principles only at this stage.
Two SDKs, published on npm.
@az54/core
The TypeScript client: requests, typed responses, webhook signature verification.
@az54/react
React bindings for the flows a front end actually renders.
Versions are on npm, not on this page — a number printed here would be wrong within a month.
What integrating looks like.
- Authentication. API keys carry only the scopes you grant them, per organization. Dashboard access is protected by two-factor authentication.
- Idempotency. You choose an `order_id`, unique within your organization. There is no idempotency header to send, and no middleware to configure.
- Webhooks. Callbacks are signed with HMAC-SHA512, retried on a bounded schedule, and every attempt is readable through the API. You can trigger a resend yourself.
- Events. A server-sent event stream, for systems that would rather listen than poll.
- Money. Every amount is an integer in the currency's smallest unit. One wallet, one currency; cross-currency movement requires an explicit FX pair.
API reference
API reference — currently French only
The reference, the endpoint list and the guides live there. It is in French today; an English version is planned and is not on this site's roadmap page because it is ours, not a product promise.