e-Sign — Leegality

What does this API do?

The Leegality e-Sign API allows lenders integrated with the ULI Platform to initiate digital signing journeys for loan documents. It creates an eSigning request for one or more invitees (signers/reviewers) and returns a unique Document ID along with signing URLs. Invitees receive signing links via SMS, Email, or WhatsApp to complete the process.

Supported eSign types include:

• Aadhaar eSign — Aadhaar OTP, Biometric, Iris, or Face verification-based digital signature.
• Virtual Sign — Mobile/Email OTP-based approval.
• DSC — USB-dongle based digital signature using a Certificate Authority-issued DSC.
• Document Signer Certificate — Server-based, organisation-level signing certificate.
• Automated Signer — Pre-configured signing using a Document Signer Certificate or Virtual Signature.
• Quick Sign — Drawn, chosen, or fingerprint-based signature for a frictionless experience.

Once all signatories have signed, the platform sends a callback notification to the lender's registered callback URL with document status and invitee details.

Who can use it?

Lenders and financial institutions onboarded on the ULI Platform who need to digitise document signing workflows for loan agreements, sanction letters, or other legal documents.

Prerequisites

Complete all common platform prerequisites as described in Getting Started with ULI Platform APIs.

In addition, the following Leegality-specific steps must be completed before calling this API:

• Leegality Account Onboarding — Complete the necessary Leegality account setup to obtain system access.
• X-Auth-Token Setup — Retrieve your X-Auth-Token from the API Settings tab on your Leegality dashboard. This is required in every API request header.
• Workflow Configuration — Define and publish at least one Workflow Profile in the Leegality dashboard. The profileId of a published workflow is mandatory in the request body.
• Template Configuration (if applicable) — If using a Template-type workflow, configure the template with any fillable fields. Alternatively, a Base64-encoded PDF can be passed directly.
• Callback URL Registration — Register a callback URL with the platform to receive post-signing webhook notifications from Leegality.

API endpoints

HTTP Method: POST

URL path convention: /{service name}/{ver}/{lang}

Headers

Request body

All requests must be in JSON format. The top-level envelope parameters are:

Key fields within the data object:

Sample request skeleton:

{
  "ts": "2025-05-01T10:00:00Z",
  "txncode": "TXN123456789",
  "ver": "1.0",
  "hmac": "<SHA-256 hash of data value>",
  "data": {
    "profileId": "<workflow-profile-id>",
    "file": {
      "name": "LoanAgreement.pdf",
      "file": "<base64-encoded-pdf>"
    },
    "invitees": [
      {
        "name": "Borrower Name",
        "email": "borrower@example.com",
        "phone": "9876543210"
      }
    ],
    "irn": "LENDER-REF-001"
  }
}

Response fields

Callback (Webhook): After each invitee signs, Leegality sends a POST to the lender's registered callback URL. Key callback body fields:

The lender's callback endpoint must return an HTTP 200 response. If not received, Leegality will retry the callback 3 times.

Error codes

For a comprehensive list of platform-level error codes, refer to the Latest Platform Error Code document.

Who to contact?

If you encounter an issue with the e-Sign API, email support@rbihub.in with the following details:

• Subject: Leegality eSign API Error
• Service Name: esign-estamp
• Environment: Sandbox or Production
• Service Provider: Leegality
• Request Headers
• Request Payload
• Error Code and Error Message
• Screenshot or log of the error
• Prerequisites status: IP Whitelisting, URL Whitelisting, Service Subscription, Token Generation