improved

Contextualise a Signer Consent Request by attaching a document

It is now possible to link a document to a Signer Consent Request by specifying a documentId when creating the Signer Consent Request. This enables the addition of a text link after documents verification at the Consents validation step in the signing flow, allowing Signers to open the document in a modal and identify which document the consent applies to.

The documentId will not be displayed in the audit trail, as the Signer Consent Request remains attached to the Signature Request.

How to Contextualise a Signer Consent Request:

  1. Upload the document – Retrieve the documentId after uploading a document via POST /signature_requests/{signatureRequestId}/documents (see API reference)
  2. Create a Signer – A Signer must be created before adding a Signer Consent Request via POST /signature_requests/{signatureRequestId}/signers (see API reference)
  3. Create a Signer Consent Request – Specify the documentId when creating the Signer Consent Request via POST /signature_requests/{signatureRequestId}/consent_requests (see API reference)

For more details, please refer to our dedicated guide section.