Unclaimed Draft Create Embedded With Template Request

Allows signers to decline to sign a document if `true`. Defaults to `false`.

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.

Add CC email recipients. Required when a CC role exists for the Template.

Client id of the app used to create the draft. Used to apply the branding and callback url defined for the app.

An array defining values and options for custom fields. Required when a custom field exists in the Template.

Use `files[]` to append additional files to the signature request being created from the template. Dropbox Sign will parse the files for [text tags](https://app.hellosign.com/api/textTagsWalkthrough) and append it to the signature request. Text tags for signers not on the template(s) will be ignored. **files** or **file_urls[]** is required, but not both.

Use file_urls[] to append additional files to the signature request being created from the template. Dropbox Sign will download the file, then parse it for [text tags](https://app.hellosign.com/api/textTagsWalkthrough), and append to the signature request. Text tags for signers not on the template(s) will be ignored. **files** or **file_urls[]** is required, but not both.

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

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

The request from this draft will not automatically send to signers post-claim if set to 1. Requester must [release](/api/reference/operation/signatureRequestReleaseHold/) the request from hold when ready to send. Defaults to `false`.

The request created from this draft will also be signable in embedded mode if set to `true`. Defaults to `false`.

The custom message in the email that will be sent to the signers.

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 preview experience (i.e. does not allow the requester's end user to add any additional fields via the editor). - `preview_only=true`: Allows requesters to enable the preview only experience. - `preview_only=false`: Allows requesters to disable the preview only experience. **NOTE:** This parameter overwrites `show_preview=1` (if set).

The email address of the user that should be designated as the requester of this draft.

The URL you want signers redirected to after they successfully request a signature.

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.

Add Signers to your Templated-based Signature Request.

The URL you want signers redirected to after they successfully sign.

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

The subject in the email that will be sent to the signers.

Use `template_ids` to create a SignatureRequest from one or more templates, in the order in which the templates will be used.

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.

Controls whether [auto fill fields](https://faq.hellosign.com/hc/en-us/articles/360051467511-Auto-Fill-Fields) can automatically populate a signer's information during signing. **NOTE:** Keep your signer's information safe by ensuring that the _signer on your signature request is the intended party_ before using this feature.

This allows the requester to specify whether the user is allowed to provide email addresses to CC when claiming the draft.