Businesses can leverage the E-sign journey to have documents e-signed by their users. This process involves two steps: first, by calling the API in Step 1, the business receives a signer's URL and a document ID. Once the user completes the signing process, the business calls a Step 2 API, providing the document ID obtained in the first step to obtained the signed document.

The following checks can be configured with the E-sign journey.

Journeys Input Output
    E-Sign Journey
  1. File ID
  2. File to be signed
  3. Signer Details
  1. E-signed document
  2. Audit Trail
  3. Signers Details