Free demo hits. Pay when you go live. Request access
Documents & Biometrics

Aadhaar Masking API

Upload an Aadhaar image or PDF and receive a copy with the first eight digits masked, as regulations require before storage. Keep only the compliant version and stop unmasked Aadhaar copies from ever landing in your systems.

Response
Real-time
Inputs
1 required
Consent
Not required
Billing
Per successful call
POST /v1/aadhaar-masking
Sandbox · Production
  1. Your application sends

    • Aadhaar image or PDF*
  2. emver API

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

  3. Verified with

    emver document intelligence

  4. You receive

    • Masked document
    • Number detected (yes/no)
    • Confidence flag
aadhaar-masking Full reference
Overview

What the Aadhaar Masking API does

Storing unmasked Aadhaar copies is a compliance risk. The Aadhaar Masking API detects the number on the document, in any orientation and on both sides, and returns a masked copy ready for storage, with a confidence flag when manual review is advisable.

Use it at every intake point, from candidate uploads to email attachments, so the compliant version is the only version.

Benefits

Why teams use the Aadhaar Masking API

Automatically mask the first eight digits on Aadhaar images and PDFs.

Compliant by default

Only masked copies reach storage.

Instant

Runs inline during upload.

Handles real documents

Rotated, both-sided and multi-page uploads.

Review flag

Low-confidence cases are surfaced instead of silently stored.

Use cases

Where it's called

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

Candidate document uploads

Mask before the file is attached to the case.

Email and WhatsApp intake

Clean attachments received over messaging channels.

Archive remediation

Mask legacy copies already in storage.

Account opening

Compliant KYC document handling.

How it works

Four steps, one response envelope

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

  1. 01

    Authenticate

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

  2. 02

    Send the inputs

    Aadhaar image or PDF as a JSON body. Optional fields sharpen the match.

  3. 03

    We verify at source

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

  4. 04

    Act on the result

    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

Aadhaar Masking API: frequently asked questions

What teams ask before adding the Aadhaar Masking API to their integration.

No. The original is processed and purged; only the masked output is returned.

Yes. Scans, photocopies, phone photos and PDFs are supported.

Related

APIs that run alongside it

Usually called with the Aadhaar Masking API, on the same key.

All APIs
Access usually set up within one working day

Start verifying with emver today.

Tell us which APIs and what monthly volume. We set up your organisation, approve the APIs with demo hits and share per-call pricing.