CCA · C-DACDocuments & SigningReady to ship

Aadhaar eSign API Integration

Apply legally-valid digital signatures to documents using Aadhaar OTP — fully paperless contract execution.

Provider
CCA · C-DAC
Version
v2.1
Uptime
99.93%
Latency
540 ms
Access
Licensed
PKILegally Valid

What Aadhaar eSign API integration does

Aadhaar eSign applies a legally valid digital signature to a document using a PKI certificate generated on demand against an Aadhaar OTP authentication. The signature holds under the Information Technology Act, and the certificate is issued by an authority licensed by the Controller of Certifying Authorities.

For any business whose process ends in a signed document, this is the step that collapses the timeline. A loan agreement, a policy document, a vendor contract, a consent artefact or a rental agreement that previously required printing, couriering, signing and scanning — three to five days in the best case — completes inside the same session as the application. The output is a tamper-evident signed PDF with an embedded certificate that any party can verify independently.

What teams build with it

Loan agreement execution

Sign the sanction letter and agreement immediately after approval so disbursal is not waiting on paperwork.

Policy issuance

Execute insurance proposals and policy documents digitally at the point of purchase.

Consent capture

Record explicit, cryptographically verifiable consent for data access, health record linkage or credit checks.

Vendor and partner contracts

Close merchant, supplier and partner agreements without a courier cycle.

Endpoints included

  • POST/esign/v2/initiate
    Starts an eSign ceremony for a document hash and returns a redirect URL.
  • GET/esign/v2/status
    Returns the completion status and signed document reference.

Try it in the sandbox

Starts an eSign ceremony for a document hash and returns a redirect URL.
POSThttps://sandbox.aeologic.io/esign/v2/initiate
Requestapplication/json
{
  "document_hash": "sha256:9b74c98...e21",
  "signer_aadhaar": "XXXX-XXXX-4827",
  "reason": "Loan Agreement #LN-7781"
}
Response
Run the sample to see a live response
Returns masked / synthetic data in Sandbox

What you need before we start

  • The document template to be signed, finalised before signature initiation
  • The signer's Aadhaar-linked mobile number for OTP delivery
  • Storage for the signed artefact that meets your retention obligations
  • A defined flow for signature declines and OTP failures

How we deliver it

  1. Document template review and signature-field placement
  2. Sandbox integration covering initiation, OTP and status polling
  3. Signed-artefact storage and verification wiring
  4. Production rollout under our licensed access, with audit trail configured

Related Documents & Signing integrations

Industries using Aadhaar eSign

Solution bundles that use it

Aadhaar eSign API integration — FAQs

Is an Aadhaar eSign signature legally valid?

Yes. It is a digital signature under the Information Technology Act, using a certificate from a CCA-licensed authority, and carries the same standing as a handwritten signature for documents it covers.

How long does signing take?

Typically under a minute end to end — the initiation call returns in roughly 500 ms and the rest is the customer receiving and entering the OTP.

What if the signer's mobile is not linked to Aadhaar?

OTP-based eSign requires the Aadhaar-linked mobile. Where that is unavailable, the usual alternative is a DSC-based signing flow, which we scope separately.

Can multiple parties sign the same document?

Yes. Multi-party signing is supported by sequencing signature requests against the same document, with each signer's certificate embedded in turn.

Ship Aadhaar eSign in days

Tell us your stack and we'll wire up Aadhaar eSign API integration for your team.

Talk to Aeologic