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

ID Document OCR API

Upload a photo or scan of an Indian ID document and receive its fields as structured data: name, number, date of birth, address and document type. Auto-fill forms, cut manual entry and feed the extracted number straight into source verification.

Response
Real-time
Inputs
1 required · 1 optional
Consent
Not required
Billing
Per successful call
POST /v1/id-document-ocr
Sandbox · Production
  1. Your application sends

    • Document image (front, and back where applicable)*
    • Expected document type
  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

    • Detected document type
    • Extracted fields (name, number, DOB, address)
    • Image quality score
    • Masked identifiers
id-document-ocr Full reference
Overview

What the ID Document OCR API does

Manual data entry from ID cards is slow and error-prone. The ID Document OCR API classifies the document, reads its fields and returns them in a clean structure, together with a quality score so blurry or cropped uploads can be rejected up front.

It is designed to sit in front of the verification APIs: extract the PAN or Aadhaar from the image, then validate it at source with a second call on the same key.

Benefits

Why teams use the ID Document OCR API

Extract structured data from Aadhaar, PAN, passport, DL, voter ID and more.

No manual entry

Forms fill themselves from the document image.

Quality gate

Reject unreadable uploads before they reach a reviewer.

Feeds verification

Extracted numbers flow into source checks with one more call.

Broad document coverage

Aadhaar, PAN, passport, driving licence, voter ID and more.

Use cases

Where it's called

Where the ID Document OCR API is typically called, and what it settles there.

Candidate and customer onboarding

Auto-fill personal details from an uploaded ID.

Mobile-first KYC

Capture and read documents on the phone camera.

Back-office digitisation

Extract data from archives of scanned documents.

Fraud triage

Flag documents whose printed data does not match declared data.

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

    Document image (front, and back where applicable) 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

ID Document OCR API: frequently asked questions

What teams ask before adding the ID Document OCR API to their integration.

OCR reads it. Genuineness comes from the source-verification APIs, which emver recommends calling with the extracted number.

Images are processed and then purged under your organisation's retention setting. Masked identifiers are returned.

Related

APIs that run alongside it

Usually called with the ID Document OCR 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.