Fetch ABHA by Aadhaar number

Find the Aadhaar number behind an ABHA number

The reverse lookup. It returns a national identity number, so treat both the request and the response as sensitive and log neither.

GET/v3/profile/benefit/search/aadhaarByAbha

Authorizations

Authorizationbearer tokenRequired

The accessToken from POST /api/hiecm/gateway/v3/sessions. Send it as Authorization: Bearer <ACCESS_TOKEN>.

Headers

REQUEST-IDstringRequired

Unique UUID v4 per request. Used for idempotency and distributed tracing. Generate a fresh UUID for every call.

TIMESTAMPstringRequired

ISO 8601 UTC timestamp of the request.

BENEFIT_NAMEstring

The benefit scheme an enrolment belongs to. Send healthid api on the enrol and search calls, and healthid on the login OTP and verify calls under Find ABHA. On the enrolment OTP request the header is present but explicitly disabled, so it is not sent there.

A login OTP request sent with healthid api rather than healthid was accepted on the sandbox on 2026-09-11, so the login calls may take either.

NHA's files spell this header four different ways and use scheme values beyond healthid. Which spelling each endpoint accepts is not confirmed against the sandbox. The Conventions page for this module lists all four.

healthIdNumberstringRequired

The 14 digit ABHA number, sent plain in the recorded request, in the dashed 91-XXXX-XXXX-XXXX form.

Responses

200

The specification does not describe this body. Send the call with Try it to see what comes back.

Find the Aadhaar number behind an ABHA number

curl --request GET \
  --url https://abhasbx.abdm.gov.in/abha/api/v3/profile/benefit/search/aadhaarByAbha \
  --header 'Authorization: Bearer <ACCESS_TOKEN_FROM_SESSIONS_CALL>' \
  --header 'REQUEST-ID: <REQUEST_ID>' \
  --header 'TIMESTAMP: <TIMESTAMP>' \
  --header 'BENEFIT_NAME: healthid api' \
  --header 'healthIdNumber: <ABHA_NUMBER>'

The specification does not describe this body. Send the call with Try it to see what comes back.