Skip to content

Published services, current details, and clear categories.

Explore APIs
FinSour
Legal4 APIsPopular

Aadhaar eSign API

Let a signer authenticate through Aadhaar, give consent, and apply a certificate-backed signature to a document inside your own journey.

Get APIBrowse eSign & Documents APIs
AGREEMENT***AADHAAR CONSENTXXXX XXXX 4321AADHAAReSIGNSIGNEDESN-0000-48212026-08-14 09:12
Request and response

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

You send

The prepared document and the signer's details, with the signer's consent to an Aadhaar-based authentication

You receive

The signed document with its signature applied, and the reference your system needs to trace the signing

Coverage
India, for signers identified by an Aadhaar-based authentication
Typical users
Lending, insurance, fintech, marketplace, logistics and HR operations teams
Coverage note
India. The authentication methods, the files returned and the document types supported depend on the data source and your service contract
Overview

What you can do with the Aadhaar eSign API

Aadhaar eSign lets someone sign a document online after an Aadhaar-based authentication identifies them. The signature applied to the file is backed by a certificate created for that signing. There is no token to issue and nothing for the signer to renew. Lenders, insurers, marketplaces, logistics networks and staffing platforms deal with customers who are never in the room. They can finish execution in the same session that produced the document, instead of emailing a copy and waiting for a scan nobody can verify. The signer sees what is being signed, authenticates, and gives explicit consent before the signature is applied. The authentication methods you can offer and the files you get back depend on the data source behind them and on your service contract.

  • What comes back after an Aadhaar eSign

    When signing completes, your application can receive the signed document, the signature applied to it, and the reference that lets you trace the transaction later. The fields and files you get can vary with the data source behind them and with your service contract.

  • eSign inside your own app

    Connect the flow to a website, a mobile app, a loan origination system, a policy administration platform or an internal dashboard. Execution then happens in the session that produced the document, instead of in a separate email thread.

  • Nothing for the signer to buy or install

    The signer needs no hardware and no certificate of their own. They authenticate, consent, and the signature is applied. That is what makes the flow workable for customers who sign once.

  • Consent stored with the signature

    You show the signer what is being signed, and they give explicit consent before the signature is applied. The consent stays with the executed file.

How it works

The five-step Aadhaar eSign API workflow

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

Step 1

Assemble the document

Your application assembles the final document and identifies the signer or signers it must reach.

Step 2

Send the signer to Aadhaar authentication

You show the signer the document, and they complete an Aadhaar-based authentication of the kind your service contract supports.

Step 3

Capture the consent to sign

The signer confirms the intent to sign and gives explicit consent for the signature to be applied to that document.

Step 4

Collect the signed file and its reference

Your application receives the signed document and a structured response carrying the reference and the signing details available.

Step 5

Carry on with the journey

Store the signed document with its audit information and let the process continue: disbursal, activation, onboarding or dispatch.

Industries

Where teams use Aadhaar eSign API

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

  • Lending and NBFC

    Loan agreements signed the moment the customer accepts

  • Insurance

    Proposal and servicing forms signed remotely by the policyholder

  • Fintech and PSP

    Merchant service agreements signed during onboarding

  • Marketplaces

    Seller agreements signed before a listing goes live

  • Logistics and fleet

    Driver-partner and vendor agreements signed at induction

  • Staffing and gig platforms

    Offer letters and contractor terms signed off-site

Used in these industries

What is Aadhaar eSign?

Aadhaar eSign is a way to sign a document online where an Aadhaar-based authentication identifies the signer. The signature applied to the document is backed by a certificate created for that signing. No hardware token is issued, and the signer has nothing to renew.

That matters most when your customers are never in the room. A borrower, a policyholder or a delivery partner can complete a document from a phone. You get back a signed file you can check later.

How an Aadhaar eSign API works

An Aadhaar eSign API puts the signing step inside the journey your application already runs. Your system prepares the document, sends the signer to authenticate, and receives the signed file with the reference it needs to trace the transaction. The agreement is finished in the session that produced it.

Most teams start by emailing the document, waiting for a scan and filing it. That works for a handful of agreements a week, then breaks down at volume, leaving the business with a copy nobody can verify.

What the signer needs to do

The flow starts from the signer. You show the signer what is about to be signed. They complete an Aadhaar-based authentication and consent to the signature being applied.

Where the method uses a one-time password, it goes to the mobile number held against the Aadhaar. Say so on your own screens.

Design the failure paths as carefully as the happy one, because completion depends on a person finishing an authentication. An unreachable number, an abandoned session and a signer who reads the document and declines all need an answer. Which authentication methods you can offer depends on your service contract.

Teams that use Aadhaar eSign

  • Lending and NBFC: execute the loan agreement and mandate paperwork when the customer accepts, without waiting on a branch visit.
  • Insurance: complete proposal forms, servicing requests and intermediary onboarding remotely, including in the field.
  • Fintech and PSP: have a merchant sign the service agreement during onboarding, and activate on a completed file.
  • Marketplaces: get seller agreements and policy acceptances signed before a listing is allowed to go live.
  • Logistics and fleet: sign driver-partner and transporter agreements at induction, usually on a phone at a hub.
  • Staffing and gig platforms: issue offer letters and contractor terms to workers who will never visit an office.
  • Real estate: complete rental and license documents and allotment letters, within the limits of electronic execution.
  • Telecom: complete channel-partner and enterprise customer documentation across a distributed sales network.

How to eSign a document online

The part the signer experiences is short:

  1. Open the document from the link or screen your application shows.
  2. Read what is being signed and confirm the intent to sign it.
  3. Authenticate with the Aadhaar-based method your contract supports.
  4. Consent to the signature being applied.
  5. Receive the signed copy, stored with its audit information.

Choosing between the signing methods

Start from the signer. Ask how often that person will sign for you, and whether anyone downstream has already said what they will accept. Then work out how much friction the journey can carry before a customer walks away.

Those answers pick the method, and the alternatives have their own pages here. Many teams work the other way round, picking a method and meeting the constraint afterwards.

Building the eSign step into your journey

Treat the signed file as the record. Store the returned document with its signature intact, and avoid re-rendering it, which can break verification.

Build for partial completion, because different people finish a multi-party document at different times. The files and fields you get back can vary with the data source behind them and with your service contract.

This flow handles personal data. Run it inside a consent framework. Collect only what the signing requires, and capture the consent in a form you can produce later.

Describe what is being signed in words the signer can read before they authenticate. Hold signed documents and their audit information under retention rules you can defend.

Indian law does not allow every document to be executed electronically. Eligibility is a legal question. Settle it with your own advisors before you automate a document type.

Restrict who inside your business can start a signing run, record who did, and withdraw that access when a role changes.

FAQ

Common questions

What teams ask before they integrate Aadhaar eSign API.

It is a way to sign a document online where an Aadhaar-based authentication identifies the signer. The signature applied to the document is backed by a certificate created for that signing, rather than by a certificate the signer holds on a token.

Related

More in eSign

Aadhaar eSign, electronic signatures, digital signature certificates and eStamp.

Browse eSign & Documents APIs
New

Digital Signature Certificate API

Bring signing by a named authorized signatory into your workflow. The signature comes from a certificate on the signatory's own token, and you can check that certificate before you rely on the document.India, for certificates held by named individuals and organization role holdersView APINew

Electronic Sign API

Send a document out for OTP signing and get the signed file back with an audit trail, ready to file against the transaction it belongs to.Documents signed by signers in IndiaView API
Get started

Add Aadhaar eSign 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.

Get APIBrowse the catalog