Enforcing Signature Capture

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

Property	Type	Editable	Required	Default	Sample Values
status	string	Yes	No	DRAFT	`DRAFT/SENT/COMPLETED/ARCHIVED/` `DECLINED/OPTED_OUT/EXPIRED`
type	string	Yes	No	PACKAGE	`PACKAGE/TEMPLATE/LAYOUT`
name	string	Yes	No	n/a	`Enforce Capture Signature Example`
documents
name	string	Yes	No	n/a	`sample doc`
approvals
fields
subtype	string	Yes	No	n/a	`FULLNAME/INITIALS/CAPTURE/` `MOBILE_CAPTURE/LABEL/TEXTFIELD/` `TEXTAREA/CHECKBOX/DATE/RADIO/` `LIST`
type	string	Yes	No	n/a	`SIGNATURE/INPUT`
extract	boolean	Yes	No	false	`true/false`
height	integer	Yes	No	50	50/100/150...
left	integer	Yes	No	0	50/100/150...
page	integer	Yes	No	0	0/1/2...
top	integer	Yes	No	0	50/100/150...
width	integer	Yes	No	200	50/100/150...
role	string	Yes	No	n/a	`Client1`
enforceCaptureSignature	boolean	Yes	No	false	`true/false`
roles
id	string	Yes	No	n/a	`Client1`
name	string	Yes	No	n/a	`Client1`
type	string	Yes	No	SIGNER	`SIGNER/SENDER`
signers
email	string	Yes	Yes	n/a	`john.smith@example.com`
firstName	string	Yes	Yes	n/a	`John`
lastName	string	Yes	Yes	n/a	`Smith`
phone	string	Yes	No	n/a	`514-555-8888`
id	string	Yes	No	n/a	`Client1`
company	string	Yes	No	n/a	`Acme Inc`
title	string	Yes	No	n/a	`Managing Director`