ABHA (Health ID) API Integration
Create and verify Ayushman Bharat Health Accounts (ABHA) and link health records under ABDM.
What ABHA (Health ID) API integration does
ABHA — the Ayushman Bharat Health Account — is the patient identity layer of India's Ayushman Bharat Digital Mission. Integration lets your platform create and verify ABHA numbers and link health records under the ABDM consent framework.
The design principle is that the patient, not the platform, controls the record. A health record linked to an ABHA can be shared with another provider only under an explicit consent artefact with a defined scope and duration. For a hospital information system, teleconsultation platform, diagnostics chain or insurer, participating means implementing that consent protocol correctly — and getting it wrong is a compliance failure rather than a bug.
The clinical payoff is continuity. A patient arriving at a new provider with a verified ABHA and linked history does not need to repeat diagnostics that were run last month, and the clinician sees prior context instead of starting blind.
What teams build with it
Patient onboarding
Create or verify an ABHA and register the patient against a national health identity rather than a local record number.
Consent-governed record linkage
Link existing records to the patient's ABHA under an explicit consent artefact with recorded scope and duration.
Care continuity
Retrieve prior history from other ABDM participants with patient consent so clinicians see context rather than re-ordering tests.
Insurance and claims
Use verified health identity and consented record access to shorten claim adjudication.
Endpoints included
POST/abdm/v3/abha/verifyValidates an ABHA number/address and returns profile basics.
Try it in the sandbox
https://sandbox.aeologic.io/abdm/v3/abha/verify{
"abha_address": "ananya@abdm",
"consent": "Y"
}What you need before we start
- Your ABDM participant position, confirmed during scoping
- A consent journey meeting ABDM presentation requirements
- A health record model that can be linked against an ABHA
- Handling for consent revocation and expiry
How we deliver it
- Scoping of your ABDM participation and the record types in scope
- Sandbox integration covering ABHA creation, verification and linkage
- Consent flow design and review against ABDM requirements
- Production rollout with consent-artefact audit logging
Industries using ABHA (Health ID)
Solution bundles that use it
ABHA (Health ID) API integration — FAQs
What is an ABHA number?
A national digital health identity that lets a citizen link and share health records across ABDM-participating providers under their own consent.
Is patient data stored by Aeologic?
No. Record exchange is brokered under the ABDM consent framework and flows between the participants involved; we do not retain clinical payloads.
What else is needed to onboard a patient end to end?
In practice Aadhaar e-KYC for identity, DigiLocker for supporting documents and Aadhaar eSign for consent capture. Our ABDM patient onboarding bundle chains exactly those steps.
Is this integration available now?
ABHA is currently in certification with our engineering team and can be included in a scoped engagement with a confirmed delivery date.
Ship ABHA (Health ID) in days
Tell us your stack and we'll wire up ABHA (Health ID) API integration for your team.
Talk to Aeologic