Integrate end to end on free demo hits — pay only when you go live.Free demo hits. Pay when you go live.
Request access
Validate a 12-digit Aadhaar number against the issuing authority and get back the demographic profile linked to it: age band, gender, state and whether a mobile is registered. No OTP, no biometric capture, no full Aadhaar stored.
Your application sends
emver API
Validates the request, queries the source, normalises the answer and logs the call. Billed only on success.
Verified with
UIDAI Aadhaar records
You receive
The Aadhaar Verification API is a demographic validation check. You send the Aadhaar number, we confirm it exists and is active, and you receive the profile attributes the authority links to it. The full number is never echoed back; only a masked version is returned so your systems never hold the complete identifier.
It is the fastest way to catch a fake, mistyped or inactive Aadhaar at the very start of onboarding, before you spend money on deeper checks or let a case move forward on bad identity data.
Consent is part of the contract
The individual must consent to Aadhaar-based verification before you call this API. emver records the consent text with every request so your audit trail is complete.
Confirm an Aadhaar number is genuine and active, without OTP friction.
Real-time response, so onboarding forms can validate identity while the person is still on the screen.
Only a masked Aadhaar and demographic attributes come back. Your database never stores the full number.
Reject invalid or inactive numbers up front and stop paying for follow-on checks on bad identities.
Consent language is attached to every call and preserved in the audit log for UIDAI compliance.
Where the Aadhaar Verification API is typically called, and what it settles there.
Validate the Aadhaar a candidate declares before the background check package starts.
First-pass identity check for wallets, lending journeys and marketplace sellers.
High-volume, low-cost identity gate for delivery and field partners.
Flag applications that reuse an Aadhaar number or present one that does not exist.
Request and response details, environments and a ready-to-import collection are in the developer console.
Call with your organisation API key. Sandbox and production use the same contract.
Aadhaar number as a JSON body. Optional fields sharpen the match.
emver queries the authoritative record, normalises the answer and logs the request.
A verification status plus the fields listed above, in the same response envelope as every other API.
Privacy and security built in
Consent recorded · Payloads not retained beyond your retention window · Every request traceable
FAQ
What teams ask before adding the Aadhaar Verification API to their integration.
No. It is a demographic validation that confirms the number is genuine and active and returns the linked attributes. If you need consent-driven document pull with the person's participation, use the DigiLocker API alongside it.
Never. Responses carry a masked form only, which keeps your systems out of scope for storing the complete identifier.
Explicit consent from the individual for Aadhaar-based verification. emver stores the consent statement with each request so it is available in the case audit trail and in your API logs.
Yes. Every organisation gets sandbox keys and demo hits in the developer console, so you can wire the integration end to end before production billing starts.
Usually called with the Aadhaar Verification API, on the same key.
Identity & KYC
Validate a PAN, match the name and confirm it is active with the tax department.
Identity & KYC
Confirm a PAN is seeded with the given Aadhaar.
Identity & KYC
Let the person share government-issued documents with consent, verified at source.
Tell us which APIs and what monthly volume. We set up your organisation, approve the APIs with demo hits and share per-call pricing.