Skip to main content
Once the patient is logged in, the PHR app owns their ABHA profile screen — name, address, linked mobile, KYC status, and the ABHA card they show at a facility.
All profile APIs need a live ABHA Gateway session. Check GET /abdm/v1/session/status before rendering the profile screen; a 491 means you need to re-authenticate.

​
Profile details

​
ABHA card and QR code

The two assets a patient actually shows at a counter. Render them directly in the app.

​
KYC

An ABHA address created via mobile OTP is not KYC-verified. Run KYC to upgrade it — required before the patient gets a 14-digit ABHA number and full record access. Profile Management overview → An ABHA address and a 14-digit ABHA number are linked through KYC — completing Aadhaar KYC on a mobile-created ABHA address associates it with the patient’s ABHA number. There is no separate de-link endpoint; deleting the profile is the terminal action.

M1 — ABHA Web SDK

The Web SDK ships the KYC flow as a themeable component if you’d rather not build the OTP screens.