v1

latestOpenAPI 3.0.3MIT2026-07-1373217576.0 KB

Template

Create Template

Creates a template that can be used in future signature requests.

If client_id is provided, the template will be created as an embedded template. Embedded templates can be used for embedded signature requests and can be edited later by generating a new edit_url with /embedded/edit_url/{template_id}.

Template creation may complete asynchronously after the initial request is accepted. It is recommended that a callback be implemented to listen for the callback event. A template_created event indicates the template is ready to use, while a template_error event indicates there was a problem while creating the template. If a callback handler has been configured and the event has not been received within 60 minutes of making the call, check the status of the request in the API dashboard and retry the request if necessary.

post/template/create

Request body

filesstring[]

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

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

file_urlsstring[]

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.

allow_reassignboolean

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.

cc_rolesstring[]

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

client_idstring

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

messagestring

The default template email message.

metadataobject

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.

subjectstring

The template title (alias).

test_modeboolean

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

titlestring

The title you want to assign to the SignatureRequest.

use_preexisting_fieldsboolean

Enable the detection of predefined PDF fields by setting the use_preexisting_fields to true (defaults to disabled, or false).

Response

successful operation