ABHA SDK Login or Create
This guide provides everything you need to integrate the ABHA SDK into your application for Create ABHA, Login with ABHA flows into your healthcare applications. It provides:- Create ABHA: Create a new ABHA using Mobile or Aadhaar.
- Login with ABHA: Login to your exisiting ABHA using PHR Address, ABHA number, Aadhaar number or Mobile number.
Implementation Example
Add the following HTML and script tags to your webpage:Core Functions
1. initAbhaApp
Initializes and renders the ABHA SDK in your specified container. Parameters:| Name | Type | Required | Description |
|---|---|---|---|
containerId | string | ✅ | The HTML element ID where the SDK will mount. |
clientId | string | ✅ | Provide clientId as ext. |
data | {accessToken: string;orgIcon?: string;linkToOrgIcon?: string;} | ⚙️ Optional | Configuration data for initializing the ABHA flow. - accessToken: Pass the access token you have generated from Connect Login API without the word Bearer. - orgIcon: Public CDN URL of your organisation’s icon to display inside the SDK url should start with https://. Example - linkToOrgIcon: Public CDN URL of the icon representing “Link ABHA to your organisation” url should start with https://. Example keys with ? are optional. |
onSuccess | (params: TOnAbhaSuccessParams) => void | ✅ | Triggered when the user successfully creates or logs in to ABHA. |
onError | (params: TOnAbhaFailureParams) => void | ✅ | Triggered when an error occurs during the ABHA flow. |
onAbhaClose | () => void | ✅ | Triggered when SDK closes. |
Callback Parameters
onSuccess Callback
The onSuccess callback is triggered when the ABHA flow completes successfully. It returns verified user details and tokens, which can be used to log in or continue the user’s session. Callback Signature:| Key | Type | Description |
|---|---|---|
response | TAuthVerifyV2Response | The complete ABHA verification response, containing session tokens, user profile, and transaction details. |
onError Callback
The onError callback is triggered whenever an ABHA flow fails or is interrupted. It provides details about the failure through structured parameters, allowing you to handle or forward the error appropriately (for example, to native apps or monitoring tools). Callback Signature:| Key | Type | Description |
|---|---|---|
error | string? | Short description of the failure or error message. |
response | TAuthVerifyV2Response? | Partial or full API response object returned from ABHA services. |
onAbhaClose Callback
The onAbhaClose callback is triggered when the ABHA SDK flow gets closed. Callback Signature:Container Styling
Ensure your container has sufficient space:Troubleshooting
Common Issues
1. SDK Not Rendering
Problem: Nothing appears in the container. Solution:- Ensure containerId matches an existing HTML element.
- Verify the SDK JS and CSS are correctly loaded.
- Check browser console for errors.
2. APIs Not Being Called
Problem: API requests are not triggered after the SDK is mounted. Solution:- Ensure that the accessToken is passed correctly (do not include the Bearer prefix) and that the token has not expired.
- To prevent CORS-related issues, ensure that your domain is whitelisted.
3. Callback Not Triggered
Problem: onSuccess, onError, onKYCSuccess, onConsentSuccess, onAbhaClose isn’t firing. Solution:- Make sure callbacks are passed as valid functions.
- Avoid race conditions (e.g., calling before SDK fully loads).
4. Styling Issues
Problem: SDK content appears misaligned or clipped. Solution:- Give your container a fixed height (e.g., 600px).
- Ensure no parent element uses overflow: hidden.

