Fetch ABHA by mobile number
Find an ABHA for somebody who does not know theirs
Takes an encrypted mobile number, Aadhaar number or biometric result and sends an OTP to the mobile on record. The response carries a txnId and a message naming the masked mobile the OTP went to, so the person can confirm it is theirs before waiting for it.
Two shapes are documented for the response: an array, which fits one mobile number mapping to several accounts, and a single object. The single-object example carries a URL of The Unique UUID v4 per request. Used for idempotency and distributed tracing. Generate a fresh UUID for every call. ISO 8601 UTC timestamp of the request. The benefit scheme an enrolment belongs to. Send A login OTP request sent with 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. Two shapes are documented; the array is the more likely of the two.profile/login/request/otp, so it likely describes a different endpoint. Expect an array, and treat the single object as unconfirmed.Authorizations
Authorizationbearer tokenRequiredaccessToken from POST /api/hiecm/gateway/v3/sessions. Send it as Authorization: Bearer <ACCESS_TOKEN>.Headers
REQUEST-IDstringRequiredTIMESTAMPstringRequiredBENEFIT_NAMEstringhealthid 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.healthid api rather than healthid was accepted on the sandbox on 2026-09-11, so the login calls may take either.Body
scopestring[]RequiredmobilestringRequiredResponses
200