Aadhaar OTP Auth API Integration
Yes/No authentication of an Aadhaar holder without disclosing demographic data — ideal for presence verification.
What Aadhaar OTP Auth API integration does
Aadhaar OTP authentication — often called Yes/No auth — confirms that a person is who they claim to be without returning any demographic data at all. UIDAI answers a single question: does this Aadhaar number, combined with this OTP, authenticate successfully? You get a yes or a no, and nothing else.
That restraint is the point. Full e-KYC returns name, address, date of birth and photograph, and once you have received that data you own the obligation to protect it. For a large class of use cases — confirming presence, authorising a step-up action, verifying a returning customer — you do not need the demographic record and should not be collecting it. Yes/No authentication gives you the assurance without the data liability, which is both better privacy practice and a materially smaller compliance surface.
What teams build with it
Step-up authentication
Require Aadhaar confirmation before a high-value action — a large transfer, a beneficiary change, a profile update — without pulling demographic data.
Presence verification
Confirm a person is physically present and consenting for attendance, benefit disbursal or service delivery.
Low-risk onboarding
Verify identity for services that do not require a full KYC record, keeping your data footprint proportionate to the risk.
Re-authentication of known customers
Confirm an existing customer at a later touchpoint when you already hold their details and only need proof of presence.
Endpoints included
POST/aadhaar/v2/authConfirms a holder's OTP without returning personal data.
Try it in the sandbox
https://sandbox.aeologic.io/aadhaar/v2/auth{
"aadhaar_number": "XXXX-XXXX-4827",
"otp": "######",
"consent": "Y"
}What you need before we start
- Consent captured in your flow, stating the purpose of the authentication
- A clear decision on why Yes/No is sufficient rather than full e-KYC
- Handling for the negative case that does not strand a legitimate customer
How we deliver it
- Review of your journey to confirm Yes/No is the right mode for each step
- Sandbox integration and consent-screen review
- Production access under Aeologic's licensed UIDAI connectivity
- Audit logging that records the authentication event without storing identity payloads
Aadhaar OTP Auth API integration — FAQs
How is this different from Aadhaar e-KYC?
e-KYC returns the demographic record; Yes/No authentication returns only whether authentication succeeded. If you do not need the customer's name and address, Yes/No is the correct and more privacy-preserving choice.
Is it faster than full e-KYC?
Yes, meaningfully — around 260 ms versus roughly 400 ms — because there is no demographic payload to assemble and return.
Do we still need a licence?
Aadhaar authentication in any mode requires licensed access. It runs under Aeologic's AUA/KUA licence, so you do not need your own.
Ship Aadhaar OTP Auth in days
Tell us your stack and we'll wire up Aadhaar OTP Auth API integration for your team.
Talk to Aeologic