In Conga Sign, signers will only be asked to draw their signature once by default. If the transaction requires multiple signatures on the document, Conga Sign will automatically replicate the first drawn signature for any subsequent signatures. However, you have the option to require your signer to draw their signature on any given capture signature. This topic will focus on enforcing signature capture at the signature level.

Enforcing Capture Signature

The sample request below shows you how to set enforceCaptureSignature: true at the approval level.

HTTP Request

POST /api/cs-packages
JS

HTTP Headers

Accept: application/json   
Content-Type: application/json   
Authorization: Bearer access_token
JS

Request Payload

------WebKitFormBoundary1bNO60n7FqP5WO4t   Content-Disposition: form-data; name="file"; filename="enforce capture signature.pdf"   Content-Type: application/pdf   %PDF-1.5   %µµµµ   1 0 obj   <>>>   endobj....   ------WebKitFormBoundary1bNO60n7FqP5WO4t   Content-Disposition: form-data; name="payload"   {   "documents": [   {   "approvals": [   {   "fields": [   {   "height": 50,   "id": "Signature1",   "left": 100,   "page": 0,   "subtype": "CAPTURE",   "top": 100,   "type": "SIGNATURE",   "width": 200   }   ],   "id": "Signature1",   "role": "signer1"   },   {   "fields": [   {   "height": 50,   "id": "Signature2",   "left": 100,   "page": 0,   "subtype": "CAPTURE",   "top": 200,   "type": "SIGNATURE",   "width": 200   }   ],   "id": "Signature2",   "role": "signer1",   "enforceCaptureSignature": true   },   {   "fields": [   {   "height": 50,   "id": "Signature3",   "left": 100,   "page": 0,   "subtype": "CAPTURE",   "top": 300,   "type": "SIGNATURE",   "width": 200   }   ],   "id": "Signature3",   "role": "signer1"   }   ],   "name": "Document1",   "id": "Document1"   }   ],   "name": "test Enforce Capture at Signature Level",   "roles": [   {   "id": "signer1",   "signers": [   {   "email": "signer1@example.com",   "firstName": "John",   "id": "signer1",   "lastName": "Smith"   }   ]   }   ],   "type": "PACKAGE",   "status": "SENT"   }   ------WebKitFormBoundary1bNO60n7FqP5WO4t--
JS

For a complete description of each field, see the Request Payload Table below.

Response Payload

{   "id": "Q6v0Tn_v62G5tfRY43VBE-TEbU4="   }
JS
  • “By default, “enforceCaptureSignature" is set to false at both the transaction and signature levels. This means you do not need to do anything if you do not want to use this feature.

  • Unlike the enforceCaptureSignature true setting in the transaction level, which requires the signer to capture the signature every capture approval, at the signature level enforceCaptureSignature only forces the signer to capture their signature when the approval contains the "true" setting.

Request Payload Table

PropertyTypeEditableRequiredDefaultSample Values
statusstringYesNoDRAFT

DRAFT/SENT/COMPLETED/ARCHIVED/ 
DECLINED/OPTED_OUT/EXPIRED 

typestringYesNoPACKAGE

PACKAGE/TEMPLATE/LAYOUT 

namestringYesNon/aEnforce Capture Signature Example 
documents
namestringYesNon/asample doc 
approvals
fields
subtypestringYesNon/aFULLNAME/INITIALS/CAPTURE/ 
MOBILE_CAPTURE/LABEL/TEXTFIELD/ 
TEXTAREA/CHECKBOX/DATE/RADIO/ 
LIST 
typestringYesNon/aSIGNATURE/INPUT 
extractbooleanYesNofalsetrue/false 
heightintegerYesNo5050/100/150...
leftintegerYesNo050/100/150...
pageintegerYesNo00/1/2...
topintegerYesNo050/100/150...
widthintegerYesNo20050/100/150...
rolestringYesNon/aClient1 
enforceCaptureSignaturebooleanYesNofalsetrue/false 
roles
idstringYesNon/aClient1 
namestringYesNon/aClient1 
typestringYesNoSIGNERSIGNER/SENDER 
signers
emailstringYesYesn/ajohn.smith@example.com 
firstNamestringYesYesn/aJohn 
lastNamestringYesYesn/aSmith 
phonestringYesNon/a514-555-8888 
idstringYesNon/aClient1 
companystringYesNon/aAcme Inc 
titlestringYesNon/aManaging Director