eSign

Prerequisites

Register once to obtain a unique ID used for all API authentications. The ID is derived from your system ID and email supplied at registration. All requests must use HTTPS (TLS 1.2+).

Registration

Provide the following KYC details: full name, state, location, country, email, organisation, organisation unit, mobile, and system ID. Mandatory: full name, email, and system ID.

After approval, generate your unique ID as: <systemID><email>

Example: system ID LOREM-IPSUM, email [email protected] → unique ID [email protected].

This unique ID is required for all eSign API calls.

Authentication

eSign APIs authenticate each request with the unique ID created during registration. Include the unique ID in every call (header or field as defined in the API reference). Use the exact value and casing; treat the ID as sensitive configuration, not client visible.

eSign APIs Documentation

All APIs related to user registration, signing document hash, getting certificate chain and user KYC status:

  • keygen/csr

  • signing/sign

  • getCertificateChain

  • getKYCStatus

eSign Postman Link:

PreviousCertificate ManagementNextConfiguration Protocol Support

Last updated