API docs for Cognito Forms are located here http://help.cognitoforms.com/webhooks

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.

Use this field to assign a sequence number to a recipient in the list of recipient parties. Use unique sequence numbers for each party starting with 1 like 1,2,3,4

Use this field to send the folder signinig in sequence or not. When false, signing emails sent to all. When true, signing email are sent to next only after prior party signs.

When you are passing as a true then, Use this field to initiate the in-person signing process which can be easily completed on any device in a matter of minutes and avoids email-based signatures where required.

Use this fieeld to freeze the recipient parties after creating a folder from the API in embedded mode. Parties are allowed to be edited only when value is false.

Use this fieeld to freeze the documents in a folder after creating a folder from the API in embedded mode. Documents are allowed to be edited only when value is false.

URL for the landing page on your website/application, which the user will be redirected to after successfully sending the folder in the embedded sending view.

URL for the landing page on your website/application, which the user will be redirected to if error comes during sending the folder in the embedded sending view.

URL for the landing page on your website/application, which the user will be redirected to after successfully signing the folder in the embedded signing view.

URL for the landing page on your website/application, which the user will be redirected to if he declines to sign the folder in the embedded signing view.

URL for the landing page your website/application, which the user will be redirected to if he chooses to sign the folder later in the embedded signing view.

URL for the landing page your website/application, which the user will be redirected to if error comes during signing the folder in the embedded signing view.

The form for which the document is to be generated.

The Id of the entry for which the document is generated.

The number of the document template to be used.