Skip to content

Published services, current details, and clear categories.

Explore APIs

Aadhaar ID OCR API

Read an uploaded Aadhaar document image and return the printed identity and address details as structured fields. Nobody retypes them into your onboarding form.

Consent capturedpurpose · customer onboardingcns_7dK2QpAADHAARXXXX XXXX 4321one-time codeentered by the customeraadhaar_numberXXXX XXXX 4321MASKED AT SOURCE***first eight digits never returned
Request and response

You confirm the required fields and consent steps with us during onboarding.

You send

An Aadhaar document image or PDF page, captured or uploaded by the applicant

You receive

Structured name, date of birth or year of birth, gender and address fields, where legible on the document

Coverage
Aadhaar documents issued in India, across the layouts and scripts the reader supports
Typical users
Lending, fintech, insurance, staffing, real estate and telecom onboarding teams
Coverage note
Reads what is printed on the image you supply; it does not confirm the record with the issuing source
Overview

What you can do with the Aadhaar ID OCR API

Aadhaar ID OCR reads an image of an Aadhaar document and returns the details printed on it as structured fields. The image can be a phone photograph, a scan or a page of a PDF. Most Indian onboarding journeys already collect an Aadhaar copy. OCR removes the step where a person reads that copy and retypes the name, date of birth and address into a form. The response can carry name, date of birth or year of birth, gender, and the address block with its components, as far as the image is legible. Available fields vary by data source and by record. Treat the output as captured information that a person can review and correct. OCR reports what is printed. It does not confirm the document with the issuing source. Where a workflow needs that assurance, pair it with a verification service, and use the separate Aadhaar Masking service to redact the number in the copy you keep.

  • Named fields your form can map

    The reader returns named values: name, date of birth or year of birth, gender, the address block and its components. Your form maps them to inputs directly. Which fields come back depends on the data source and the individual record.

  • Built for phone-camera uploads

    Applicants photograph documents in poor light, at an angle, through lamination and inside a chat window. The reading step is built for those inputs and returns what it can read, even when one line is unclear.

  • Pairs with Aadhaar Masking

    Aadhaar ID OCR turns the document into fields you can act on. The separate Aadhaar Masking service redacts the number in the copy you retain. Most teams run both: structured data into the workflow, a masked copy into the archive.

  • A capture step that comes before verification

    OCR reports what is printed on the image supplied. It does not confirm the document against the issuing source. Place it before a verification and consent step in your flow, not in place of one.

How it works

The five-step Aadhaar ID OCR API workflow

Our team walks you through the exact request and response for this service during onboarding.

Step 1

Capture the Aadhaar copy with consent

The applicant photographs or uploads the Aadhaar document inside your app, web journey, agent tool or chat flow. Record consent for the purpose you are collecting it for.

Step 2

Send the image to the API

Your application submits the captured file. Supported formats and size limits depend on the selected service contract.

Step 3

Read the name, date of birth and address

The printed details that could be read come back as labeled fields, along with an indication of what could not be read.

Step 4

Let the applicant fix a misread line

Show the values back to the applicant or a reviewer. They can fix a misread character before it enters your records.

Step 5

Carry the details into KYC

Pass the confirmed details into your onboarding, underwriting or KYC workflow, and retain only the redacted copy your retention policy allows.

Industries

Where teams use Aadhaar ID OCR API

These sectors build the check into a decision they already make.

  • Lending and NBFCs

    Start an application file from the borrower's uploaded copy

  • Fintech and PSPs

    Cut a mobile signup down to a photo and a confirmation screen

  • Insurance

    Capture proposer name and address consistently at proposal stage

  • Staffing and gig platforms

    Enroll field and delivery workers from a phone camera

  • Real estate

    Record tenant and buyer details during document collection

  • Telecom

    Read subscriber details during retail or doorstep signup

What Aadhaar ID OCR does

Aadhaar ID OCR reads an image of an Aadhaar document and returns the printed details as structured fields your application can use directly. The image can be a photograph taken on a phone, a flatbed scan or a page of a PDF.

Almost every Indian onboarding journey already asks for an Aadhaar copy. Without OCR, someone still has to read that copy and retype the name, the date of birth and the address. The job falls either to the applicant on a small screen or to an operations agent working through a queue.

Both routes introduce typing errors. Both also add friction at the exact point in a signup where people give up.

Does Aadhaar ID OCR verify the document?

No. OCR reports what appears on the file you supplied. It does not establish that the document is genuine, that it is current, or that the printed details match the record held by the issuing source.

That decides where the step belongs in your flow. Treat the output as captured data, not a verified identity.

Where a decision depends on assurance, pair the reading step with a verification service and the consent flow that service requires. Run together, OCR removes the typing and verification carries the confidence.

Which Aadhaar fields come back

The response may carry the name, the date of birth or year of birth, gender, the address block and its components, and the identifier printed on the card. What you get depends on the document and on the reader behind the service. The fields on offer vary by data source and by record.

Older layouts, regional-language printing, lamination glare and low-contrast photographs all change what can be read. Treat each field as available information a person can correct before it is committed to your records.

Masking the Aadhaar number in the copy you store

Reading a document and retaining it are separate obligations. Indian KYC practice expects the Aadhaar number to be redacted in a copy an organization stores.

So a masking step sits alongside this one. Aadhaar ID OCR gives you data your workflow can act on, and the separate Aadhaar Masking service gives you an image you are allowed to keep. Most teams run both on a single upload and file the two results separately.

What makes an Aadhaar photo readable

Capture quality decides most of the outcome. A frame that holds the whole document, reasonable focus, even lighting and no direct glare on the lamination reads far better than a hurried snapshot across a counter. Where the address sits on the reverse, capture that side too.

Build the retake into the capture screen. A reshoot while the applicant is still in the journey costs a moment, and getting the document back afterwards costs a phone call.

Onboarding journeys that read Aadhaar copies

  • Lending and NBFCs. Open a loan file from the copy the borrower already uploaded. Underwriting then starts from clean fields instead of an image in a document store.
  • Fintech and payment service providers. Cut a mobile signup down to a photograph and a confirmation screen, which matters most on the small screens where these journeys actually happen.
  • Insurance. Capture proposer name and address the same way at proposal stage, where a mistyped address later becomes an undelivered policy document.
  • Staffing and gig platforms. Enroll delivery riders, field agents and contract workers from a phone camera, often at a doorstep with no desk in sight.
  • Real estate. Record tenant and buyer details during document collection, where the alternative is a photocopy and a paper register.
  • Telecom. Read subscriber details during retail or doorstep signup so the form matches the document without a second visit.

Where to place the read step in your signup

Read the document immediately after capture, while the applicant is present and can retake a poor image or fix a misread character.

Plan for partial results. A response that fills most of the fields and leaves one or two blank is a normal outcome. Send it to a short review screen.

Keep a small human queue for documents that cannot be read at all, and shrink it by improving the capture step instead of adding reviewers. Where documents arrive in batches from a channel partner, run them through the same path as single uploads so one set of rules covers both.

An Aadhaar document is personal data, and reading it is a processing activity. Collect it for a stated purpose, with the applicant's consent, and use it for that purpose alone.

Restrict who can open the raw image, and log access. Retain the file only as long as your own policy and the KYC rules that apply to your business allow.

Where the number itself is not needed for the decision in front of you, do not carry it forward into other systems.

FAQ

Common questions

What teams ask before they integrate Aadhaar ID OCR API.

An interface that accepts an image of an Aadhaar document and returns the details printed on it as structured fields. Your application reads the values from the document. No one has to type them in by hand.

Get started

Add Aadhaar ID OCR API to your workflow

Tell us how you plan to use it. Our team sets up API access, agrees your pricing and takes you through onboarding.