Skip to content

Latest commit

 

History

History
34 lines (29 loc) · 7.16 KB

UnclaimedDraftCreateRequest.md

File metadata and controls

34 lines (29 loc) · 7.16 KB
Raw

# UnclaimedDraftCreateRequest

Properties

Name Type Description Notes
type*required string The type of unclaimed draft to create. Use send_document to create a claimable file, and request_signature for a claimable signature request. If the type is request_signature then signers name and email_address are not optional.
files Array<RequestFile> Use files[] to indicate the uploaded file(s) to send for signature.

This endpoint requires either files or file_urls[], but not both.
fileUrls Array<string> 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.
allowDecline boolean Allows signers to decline to sign a document if true. Defaults to false. [default to false]
attachments Array<SubAttachment> A list describing the attachments
ccEmailAddresses Array<string> The email addresses that should be CCed.
clientId string Client id of the app used to create the draft. Used to apply the branding and callback url defined for the app.
customFields Array<SubCustomField> When used together with merge fields, custom_fields allows users to add pre-filled data to their signature requests.

Pre-filled data can be used with "send-once" signature requests by adding merge fields with form_fields_per_document or Text Tags while passing values back with custom_fields together in one API call.

For using pre-filled on repeatable signature requests, merge fields are added to templates in the Dropbox Sign UI or by calling /template/create_embedded_draft and then passing custom_fields on subsequent signature requests referencing that template.
fieldOptions SubFieldOptions
formFieldGroups Array<SubFormFieldGroup> 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.
formFieldRules Array<SubFormFieldRule> Conditional Logic rules for fields defined in form_fields_per_document.
formFieldsPerDocument Array<SubFormFieldsPerDocumentBase> 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
hideTextTags boolean Send with a value of true if you wish to enable automatic Text Tag removal. Defaults to false. When using Text Tags it is preferred that you set this to false and hide your tags with white text or something similar because the automatic removal system can cause unwanted clipping. See the Text Tags walkthrough for more details. [default to false]
message string The custom message in the email that will be sent to the signers.
metadata { [key: string]: any; } 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.
showProgressStepper boolean When only one step remains in the signature request process and this parameter is set to false then the progress stepper will be hidden. [default to true]
signers Array<SubUnclaimedDraftSigner> Add Signers to your Unclaimed Draft Signature Request.
signingOptions SubSigningOptions
signingRedirectUrl string The URL you want signers redirected to after they successfully sign.
subject string The subject in the email that will be sent to the signers.
testMode boolean Whether this is a test, the signature request created from this draft will not be legally binding if set to true. Defaults to false. [default to false]
usePreexistingFields boolean Set use_text_tags to true to enable Text Tags parsing in your document (defaults to disabled, or false). Alternatively, if your PDF contains pre-defined fields, enable the detection of these fields by setting the use_preexisting_fields to true (defaults to disabled, or false). Currently we only support use of either use_text_tags or use_preexisting_fields parameter, not both. [default to false]
useTextTags boolean Set use_text_tags to true to enable Text Tags parsing in your document (defaults to disabled, or false). Alternatively, if your PDF contains pre-defined fields, enable the detection of these fields by setting the use_preexisting_fields to true (defaults to disabled, or false). Currently we only support use of either use_text_tags or use_preexisting_fields parameter, not both. [default to false]
expiresAt number When the signature request will expire. Unsigned signatures will be moved to the expired status, and no longer signable. See Signature Request Expiration Date for details.

Note: This does not correspond to the expires_at returned in the response.

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