To create a new Template, check out the Template setup walkthrough.

If you do not have a paid API plan, your signature request will be sent in test mode only (non-legally-binding).

Example: "ATTN: Non-disclosure agreement for your signature"

This will display in the email's body.

The URL you want the signer redirected to after they successfully sign.

Example: "Signature request from NDA Template"

Allows you to pass a hidden key/value pair that will be stored with this signature_request. This parameter is for the name of the 1st hidden value.

Allows you to pass a hidden key/value pair that will be stored with this signature_request. This parameter is for the value of the 1st hidden metadata field.

Allows you to pass a hidden key/value pair that will be stored with this signature_request. This parameter is for the name of the 2nd hidden metadata field.

Allows you to pass a hidden key/value pair that will be stored with this signature_request. This parameter is for the value of the 2nd hidden metadata field.

API docs for Dropbox Sign are located here https://developers.hellosign.com/

Requests can only be made to domains associated by this application.

These params will be URL-encoded and appended to the URL when making the request.

Authentication headers are included automatically

Zapier will apply these optional headers and values to the request in addition to any headers created as part of the authentication mechanism.

Zapier will pass this along raw. If you would like to provide complex JSON, try a "Code by Zapier" step to build the structure and pass it along here. For example, {"foo": "bar"} is perfectly valid.

Determines which App Extensions will appear in the dropdown below.