Client id of the app you're using to create this draft. Used to apply the branding and callback url defined for the app.

Use files[] to indicate the uploaded file(s) to send for signature.

This endpoint requires either files or file_urls[], but not both.

Use file_urls[] to have Dropbox Sign download the file(s) to send for signature.

This endpoint requires either files or file_urls[], but not both.

This allows the requester to specify whether the user is allowed to provide email addresses to CC when creating a template.

Allows signers to reassign their signature requests to other signers if set to true. Defaults to false.

NOTE: Only available for Premium plan and higher.

A list describing the attachments

The CC roles that must be assigned when using the template to send a signature request

This allows the requester to specify editor options when a preparing a document

This allows the requester to specify field options for a signature request.

Provide users the ability to review/edit the template signer roles.

Provide users the ability to review/edit the template subject and message.

Group information for fields defined in form_fields_per_document. String-indexed JSON array with group_label and requirement keys. form_fields_per_document must contain fields referencing a group defined in form_field_groups.

Conditional Logic rules for fields defined in form_fields_per_document.

The fields that should appear on the document, expressed as an array of objects. (For more details you can read about it here: Using Form Fields per Document.)

NOTE: Fields like text, dropdown, checkbox, radio, and hyperlink have additional required and optional parameters. Check out the list of additional parameters for these field types.

• Text Field use SubFormFieldsPerDocumentText
• Dropdown Field use SubFormFieldsPerDocumentDropdown
• Hyperlink Field use SubFormFieldsPerDocumentHyperlink
• Checkbox Field use SubFormFieldsPerDocumentCheckbox
• Radio Field use SubFormFieldsPerDocumentRadio
• Signature Field use SubFormFieldsPerDocumentSignature
• Date Signed Field use SubFormFieldsPerDocumentDateSigned
• Initials Field use SubFormFieldsPerDocumentInitials
• Text Merge Field use SubFormFieldsPerDocumentTextMerge
• Checkbox Merge Field use SubFormFieldsPerDocumentCheckboxMerge

Add merge fields to the template. Merge fields are placed by the user creating the template and used to pre-fill data by passing values into signature requests with the custom_fields parameter. If the signature request using that template does not pass a value into a merge field, then an empty field remains in the document.

The default template email message.

Key-value data that should be attached to the signature request. This metadata is included in all API responses and events involving the signature request. For example, use the metadata field to store a signer's order number for look up when receiving events for the signature request.

Each request can include up to 10 metadata keys (or 50 nested metadata keys), with key names up to 40 characters long and values up to 1000 characters long.

This allows the requester to enable the editor/preview experience.

• show_preview=true: Allows requesters to enable the editor/preview experience.
• show_preview=false: Allows requesters to disable the editor/preview experience.

When only one step remains in the signature request process and this parameter is set to false then the progress stepper will be hidden.

An array of the designated signer roles that must be specified when sending a SignatureRequest using this Template.

Disables the "Me (Now)" option for the person preparing the document. Does not work with type send_document. Defaults to false.

The template title (alias).

Whether this is a test, the signature request created from this draft will not be legally binding if set to true. Defaults to false.

The title you want to assign to the SignatureRequest.