Skip to content

Aadhaar Verification API

Popular

Confirm a customer's Aadhaar identity in a consent-led flow, and use the structured result inside your own onboarding journey.

Overview

Aadhaar verification confirms that the Aadhaar identity a customer presents is in a usable state. It also checks that the details they have given match the record held against it, in a flow the holder authorizes first. It is the check most Indian onboarding journeys are built around. An API puts that check inside your own application. Your product captures consent and the required details, and the request goes to a trusted data source. A structured result comes back for your flow to route on. Nobody has to read a document image that arrived by email. Basic and Advanced coverage differ in how much the holder releases. What each can return depends on the selected service contract, and available fields vary by data source and record.

Category
KYC Services
Coverage
India, in a consent-led flow. Eligibility and tier depend on the selected service contract.
Input
An Aadhaar number with a consent record, plus the details to compare or the code the holder releases
Output
A structured status, a match outcome, and released identity details on the Advanced tier. Available fields vary by data source and record.
Typical users
Lenders and NBFCs, fintech and payment platforms, insurers, telecom operators, staffing and gig platforms
Coverage note
Consent-led only. Eligibility, tier and returned detail depend on the selected service contract.

The overview and the sections after the reference are the FinSour API catalog’s own record for this service, rendered unaltered.

Reference in progress

The request and response reference for this endpoint is not published yet.

Everything below this block is the live catalog record for this service, and it is accurate. The platform’s published API contract does not include this service yet, so there is no request or response detail to document. Rather than fill these sections with a plausible example, the page lists what is missing:

Endpoint URL and method
The host, path and HTTP verb for this service.
Authentication
How a request identifies itself, and where credentials come from.
Request parameters
Field names, types, which are required, and validation rules.
Response schema
The success body, field by field, with a real example.
Error codes
What each failure means and which are worth retrying.
Rate limits
Request ceilings, and what happens at the ceiling.

No sample payload, URL, response body, error code, rate limit or latency figure appears anywhere on this site unless it has been supplied and attributed. Each item in this list is removed only when its own detail arrives; none of them is held back to wait for the rest, and none is ever placed beside a guess in the meantime.

Use cases

  • Lending and NBFC - settle applicant identity before underwriting begins
  • Fintech and PSP - establish identity before account limits are raised
  • Insurance - confirm the proposer identity on a new proposal
  • Telecom - verify a subscriber before a connection is activated
  • Staffing and gig platforms - verify a worker before the first shift
  • Healthcare - keep patient records attached to the right person

What this service does

  • Consent comes first and stays attached

    The check is designed to run only after the holder has authorized it for a stated purpose. The consent record, the request and the result stay together. A reviewer can see all three later.

  • What an Aadhaar check returns

    A structured status, a match outcome for customer-supplied details, and on the Advanced tier the identity details the holder releases along with a masked reference. The fields available may vary by data source and by record.

  • Every outcome has a route

    A decline, an unreachable mobile number and a mismatch each come back as a distinct result. Your journey can offer an alternative document path instead of dead-ending on a retry.

  • Store a masked reference in place of the number

    The masked reference is designed to be kept instead of the full Aadhaar number. Your systems then hold what the workflow needs, without collecting sensitive data you have to protect.

How a check runs

  1. Capture informed consent

    Show the purpose in your own interface and record the customer's authorization for it. Keep the consent record joined to the request that follows.

  2. Send the number and the details to compare

    Send the Aadhaar number with the details your flow needs compared, or start the holder-authorized step where the selected tier supports it.

  3. Complete the holder-authorized step

    On the Advanced tier, the customer enters the one-time code sent to the mobile number attached to their record. That releases the details for the stated purpose.

  4. Take the status and match outcome

    Your application receives the status, the match outcome and any released details in a structured response, ready to handle in code.

  5. Route the customer and store the outcome

    Proceed, ask for an alternative officially valid document, or send the case to a reviewer. Retain the outcome with a masked reference, not the full identity.

Questions

What is an Aadhaar Verification API?
It lets your business run a consent-led Aadhaar check inside its own application, instead of collecting a document image and reviewing it by hand. Your product submits the request and receives a structured result it can act on directly.
Does the API give my business access to a government database?
No. A consented request is carried to a trusted data source and a structured result comes back. There is no direct access to a government system, and nothing comes back beyond what the holder's authorization covers.
What is the difference between the Basic and Advanced tiers?
Basic confirms the submitted number is in a usable state and can report a match outcome for customer-supplied details. Advanced adds the holder-authorized step that releases identity details, and can return a masked reference. What each tier covers depends on the selected service contract.
Is customer consent required for an Aadhaar check?
Yes, the check is designed to run only where the holder has given informed consent for that specific purpose. Keep consent specific, recorded and revocable. Your business stays responsible for the notices it shows its customers.
What happens if the customer declines or cannot complete the check?
The response separates that outcome from a mismatch. Your journey can route it. Design an alternative officially valid document path for customers who decline or whose record is not reachable, and treat it as a normal route.
What can an Aadhaar verification response contain?
A structured status, a match outcome, and on the Advanced tier the demographic details the holder releases together with a masked reference. Available fields vary by data source and record, and the response may report a comparison result in place of the underlying values.

Catalog entry last updated .