POST
/
esignature
Create E-Sign Request
curl --request POST \
  --url https://sandbox.cashfree.com/verification/esignature \
  --header 'Content-Type: application/json' \
  --header 'x-client-id: <api-key>' \
  --header 'x-client-secret: <api-key>' \
  --data '{
  "verification_id": "ABC00123",
  "document_id": 36,
  "notification_modes": "email",
  "auth_type": "AADHAAR",
  "expiry_in_days": "2",
  "capture_location": false,
  "signers": [
    {
      "name": "John Doe",
      "email": "John.Doe@email.com",
      "phone": "9999999999",
      "sequence": 1,
      "aadhaar_last_four_digit": "6789",
      "sign_positions": [
        {
          "page": 1,
          "top_left_x_coordinate": 100,
          "bottom_right_x_coordinate": 200,
          "top_left_y_coordinate": 180,
          "bottom_right_y_coordinate": 120
        },
        {
          "page": 2,
          "top_left_x_coordinate": 100,
          "bottom_right_x_coordinate": 200,
          "top_left_y_coordinate": 180,
          "bottom_right_y_coordinate": 120
        }
      ]
    }
  ]
}'
{
  "status": "SUCCESS",
  "verification_id": "ABC00123",
  "reference_id": 33,
  "document_id": 36,
  "signing_link": "SIGNING_LINK"
}

Authorizations

​
x-client-id
string
header
required

Your unique client identifier issued by Cashfree. You can find this in your Merchant Dashboard.

​
x-client-secret
string
header
required

The secret key associated with your client ID. Use this to authenticate your API requests. You can find this in your Merchant Dashboard.

Headers

​
x-cf-signature
string

Send the signature if IP is not whitelisted.

Body

application/json

Find the request parameters to add the details of the document and signer

The body is of type object.

Response

200
application/json

Success response for creating an e-signature request

The response is of type object.