Skip to content

Latest commit

 

History

History
30 lines (22 loc) · 3.65 KB

SignatureRequestSendWithTemplateRequest.md

File metadata and controls

30 lines (22 loc) · 3.65 KB
Raw

SignatureRequestSendWithTemplateRequest

Properties

Name Type Description Notes
template_ids*required [str] Use template_ids to create a SignatureRequest from one or more templates, in the order in which the template will be used.
signers*required [SubSignatureRequestTemplateSigner] Add Signers to your Templated-based Signature Request.
allow_decline bool Allows signers to decline to sign a document if true. Defaults to false. [default to False]
ccs [SubCC] Add CC email recipients. Required when a CC role exists for the Template.
client_id str Client id of the app to associate with the signature request. Used to apply the branding and callback url defined for the app.
custom_fields [SubCustomField] An array defining values and options for custom fields. Required when a custom field exists in the Template.
files [file_type] Use files[] to indicate the uploaded file(s) to send for signature.

This endpoint requires either files or file_urls[], but not both.
file_urls [str] 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.
is_qualified_signature bool Send with a value of true if you wish to enable Qualified Electronic Signatures (QES), which requires a face-to-face call to verify the signer's identity.<br>
Note: QES is only available on the Premium API plan as an add-on purchase. Cannot be used in test_mode. Only works on requests with one signer.		 [default to False]
is_eid bool Send with a value of true if you wish to enable electronic identification (eID), which requires the signer to verify their identity with an eID provider to sign a document.<br>
Note: eID is only available on the Premium API plan. Cannot be used in test_mode. Only works on requests with one signer.		 [default to False]
message str The custom message in the email that will be sent to the signers.
metadata {str: (bool, date, datetime, dict, float, int, list, str, none_type)} 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.
signing_options SubSigningOptions
signing_redirect_url str The URL you want signers redirected to after they successfully sign.
subject str The subject in the email that will be sent to the signers.
test_mode bool Whether this is a test, the signature request will not be legally binding if set to true. Defaults to false. [default to False]
title str The title you want to assign to the SignatureRequest.

[Back to Model list] [Back to API list] [Back to README]