Emver
Emver
Profiden+ Blog
Identity & KYC

Aadhaar Verification API

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.

Response
Real-time
Inputs
1 required
Consent
Recorded per request
Billing
Per successful call
POST /v1/aadhaar-verification
Sandbox · Production
  1. Your application sends

    • Aadhaar number*
  2. Profiden API

    Validates the request, queries the source, normalises the answer and logs the call. Billed only on success.

  3. Verified with

    UIDAI Aadhaar records

  4. You receive

    • Verification status
    • Masked Aadhaar
    • Age band
    • Gender
    • Issuing state
    • Mobile linked (yes/no)
aadhaar-verification Full reference

What the Aadhaar Verification API does

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. Profiden records the consent text with every request so your audit trail is complete.

Benefits of the Aadhaar Verification API

Confirm an Aadhaar number is genuine and active, without OTP friction.

Instant answer

Real-time response, so onboarding forms can validate identity while the person is still on the screen.

Privacy by default

Only a masked Aadhaar and demographic attributes come back. Your database never stores the full number.

Cheaper downstream

Reject invalid or inactive numbers up front and stop paying for follow-on checks on bad identities.

Consent captured

Consent language is attached to every call and preserved in the audit log for DPDP and UIDAI compliance.

Use cases

Aadhaar Verification API use cases

Where the Aadhaar Verification API is typically called, and what it settles there.

Employee onboarding

Validate the Aadhaar a candidate declares before the background check package starts.

Customer and merchant KYC

First-pass identity check for wallets, lending journeys and marketplace sellers.

Gig partner sign-up

High-volume, low-cost identity gate for delivery and field partners.

Fraud screening

Flag applications that reuse an Aadhaar number or present one that does not exist.

How the Aadhaar Verification API works

Request and response details, environments and a ready-to-import collection are in the developer console at console.profiden.com.

01

Authenticate

Call with your organisation API key. Sandbox and production use the same contract.

02

Send the inputs

Aadhaar number as a JSON body. Optional fields sharpen the match.

03

We verify at source

Profiden queries the authoritative record, normalises the answer and logs the request.

04

Act on the result

A verification status plus the fields listed above, in the same response envelope as every other API.

Built for the DPDP Act 2023

Consent recorded · Payloads not retained beyond your retention window · Every request traceable

Encryption in transit and at rest
Data processed in India
Per-request audit trail
Masked identifiers in responses

Aadhaar Verification API: frequently asked questions

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. Profiden 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.

Related APIs

APIs that usually run alongside the Aadhaar Verification API, on the same key.

All APIs

Get access to the Aadhaar Verification API

Tell us your use case and expected volume. We set up the organisation, share per-call pricing and issue keys.