Send Request (E-Sign)

API reference

curl -X POST "https://__mock__/esign/v1/esign/esign/send-request"

{
  "redirection_url": "string"
}

{
  "detail": {},
  "message": "string"
}

{
  "detail": {},
  "message": "string"
}

{
  "error": "string"
}

Overview

Call POST /esign/v1/esign/esign/send-request from your backend with Authorization: Bearer <token> and multipart/form-data containing aadhar_name, redirect_url, session_id, user_id, and file (PDF) per OpenAPI. On 200 OK, read redirection_url and send the user there HTTPS (opaque, sensitive URL).

Key features

• Hosted signing: User completes signer UX at KwikID-controlled pages.
• Return path: redirect_url brings the user back to your app after signing.

Implementation

Step 1: Call from your backend

Build multipart with all required fields.

Step 2: Redirect the user

Open redirection_url in the browser session. Do not log full URL in analytics.

Step 3: Fetch the signed artifact

After completion, call Get Signed File with txn_id from your integration contract (returned where your flow provides it).

Error handling

Security notes

• Never expose Bearer token to the browser.

Benefits

• Matches regulated e-sign UX while keeping API secrets server-side.

Next steps

• Get Signed File
• Verification API index