Aadhaar e-KYC API Integration
Paperless identity verification against the UIDAI database via OTP or biometric authentication. Licensed AUA/KUA access.
What Aadhaar e-KYC API integration does
Aadhaar e-KYC is the fastest legally recognised way to establish who a customer is in India. Instead of collecting an ID document, scanning it and having someone check it, you authenticate the individual directly against the UIDAI database and receive a signed demographic record — name, date of birth, gender, address and photograph — returned by the authority itself. What used to be a two-day verification queue becomes a step inside the signup form.
The obstacle has never been the API. It is the licence. Aadhaar authentication is restricted to entities operating as an Authentication User Agency or KYC User Agency, and that accreditation involves an application, a security audit and a certification cycle that most teams cannot absorb into a product roadmap. Aeologic holds licensed AUA/KUA access, so your integration is against our endpoints and the licensing burden stays with us.
We support OTP, biometric and demographic authentication modes. OTP is the common choice for remote digital onboarding; biometric suits assisted and branch-based flows; demographic matching is used where you already hold the customer's details and need confirmation rather than retrieval.
What teams build with it
Digital account opening
Banks, NBFCs and brokerages open an account in a single session — authenticate with an OTP, receive the e-KYC record, and populate the application without a document upload or a video call.
Insurance proposer verification
Confirm the proposer's identity and address at quote time so the policy can be issued immediately rather than held pending verification.
Gig and field workforce onboarding
Verify delivery partners, drivers and field agents before their first shift, with a record that satisfies platform due-diligence obligations.
Re-verification and periodic KYC
Refresh a customer file against the authoritative record when a periodic review falls due, instead of asking the customer to submit documents again.
Endpoints included
POST/aadhaar/v2/otpTriggers an OTP to the mobile number linked with the Aadhaar number.POST/aadhaar/v2/ekycReturns demographic + photo on successful OTP verification with explicit consent.
Try it in the sandbox
https://sandbox.aeologic.io/aadhaar/v2/otp{
"aadhaar_number": "XXXX-XXXX-4827",
"consent": "Y",
"transaction_id": "AEO-TXN-9f3c2a1b"
}What you need before we start
- A defined purpose for the authentication, with customer consent captured in your flow
- A regulated or contractual basis for collecting identity data under your own compliance policy
- An endpoint to receive the e-KYC response, plus storage that meets your retention policy
- Agreement on the authentication mode — OTP, biometric or demographic — for each journey
How we deliver it
- Scoping call: which modes you need, expected volume, and where the flow sits in your product
- Sandbox access with synthetic responses so your team builds and tests without live Aadhaar data
- Consent-screen and error-state review against UIDAI presentation requirements
- Production cutover under our AUA/KUA licence, with audit logging configured to your retention policy
Related Identity & KYC integrations
Industries using Aadhaar e-KYC
Solution bundles that use it
Aadhaar e-KYC API integration — FAQs
Do we need our own AUA or KUA licence?
No. Aeologic holds licensed AUA/KUA access and you integrate through it. This is the single largest time saving in the project — accreditation on your own typically runs several months.
Is the Aadhaar number stored anywhere in the flow?
Our connector is pass-through and does not retain the Aadhaar number or the demographic payload beyond the audit metadata UIDAI requires. What you store on your side is governed by your own policy, and we recommend storing the reference rather than the number.
What is the typical response time?
Around 400 ms for the e-KYC call in production. The OTP round trip depends on SMS delivery to the customer, which is the part outside anyone's control.
What happens if the customer's mobile is not linked to their Aadhaar?
OTP authentication will fail, because the OTP is delivered to the Aadhaar-linked number. The usual fallback is biometric authentication in an assisted setting, or an alternative KYC path such as CKYC or DigiLocker.
Ship Aadhaar e-KYC in days
Tell us your stack and we'll wire up Aadhaar e-KYC API integration for your team.
Talk to Aeologic