Send Document From Reusable Template

Comma-separated response fields to include.

A name for the document you are sending

List of email recipients to share the document with

A message for all signers

Whether the document should be signed in person

Document callback url. The URL will receive a POST for each of the following document events: created , viewed , signed , executed , voided , declined . Note that due to the asynchronous nature of processing, the order in which the document callbacks are sent is not guaranteed. Only HTTP ports 80, 8000-8099, 3000-3009 and HTTPS port 443 is supported. Basic auth is also supported. Ex. “ me:[email protected]:8001/callback ”. ex. callback when document is viewed { "callbackType":"Document", "id":"edc7823a-7b99-45d7-9c3c-c7dc81f8dbf2", "event":"viewed", "documentState":"pending", "createdAt":"2016-11-14T13:45:23.199-08:00" }

Document signers

Role name. For text tags, the role name in the request must correspond to the recipient name given as the second argument (name) in the text tag. When signer sequencing is enabled, the role name must match the signer name set on the template.

Signer name

Signer email

A signer can be omitted if set to true and if signer_sequencing is enabled

Is signer the owner of document?

Custom message to signer.

Merge Field Identifier. By specifying it to “name” API user can map merge field value with the name instead of merge field id

Merge Fields

Merge Field ID

Merge Field Name. This is the name provided to the merge field on the webapp, while creating the template. If it matches more than one merge field component in template all of them will be filled with the same value

Merge Field value. If the merge field is a date, the value should be in yyyy/mm/dd or yyyy-mm-dd format.

Document expiration. Must be between 1 and 365 days

Document pin. Must be between 10000 and 99999

Optional key value tags for categorization

Enable KBA on the document (applicable for KBA enabled plans)

Merge Field ID