For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Dropbox Sign WebSDKsSign Up
DocumentationAPIChangelog
DocumentationAPIChangelog
  • API Quickstart
  • API Reference
    • Welcome
    • Authentication
    • Account
    • Signature Request
      • GETGet Signature Request
      • GETList Signature Requests
      • GETDownload Files
      • GETDownload Files as Data Uri
      • GETDownload Files as File Url
      • POSTSend Signature Request
      • POSTSend with Template
      • POSTBulk Send with Template
      • POSTSend Request Reminder
      • POSTRelease On-Hold Signature Request
      • POSTUpdate Signature Request
      • POSTCancel Incomplete Signature Request
      • POSTRemove Signature Request Access
      • POSTEmbedded Bulk Send with Template
      • POSTCreate Embedded Signature Request
      • POSTCreate Embedded Signature Request with Template
      • PUTEdit Signature Request
      • PUTEdit Embedded Signature Request
      • PUTEdit Embedded Signature Request with Template
      • PUTEdit Signature Request With Template
    • Template
    • Bulk Send Job
    • Report
    • Team
    • Unclaimed Draft
    • Embedded
    • API App
    • Fax
    • Fax Line
  • Manual Reference Pages
    • Warnings and Errors
    • Constants
    • Search
    • Premium Branding
    • Expiration
    • Glossary
LogoLogo
Dropbox Sign WebSDKsSign Up
API ReferenceSignature Request

Send Signature Request

||View as Markdown|
POST
https://api.hellosign.com/v3/signature_request/send
POST
/v3/signature_request/send
$curl -X POST 'https://api.hellosign.com/v3/signature_request/send' \
>  -u 'YOUR_API_KEY:' \
>  -F 'files[0]=@mutual-NDA-example.pdf' \
>  -F 'title=NDA with Acme Co.' \
>  -F 'subject=The NDA we talked about' \
>  -F 'message=Please sign this NDA and then we can discuss more. Let me know if you have any questions.' \
>  -F 'signers[0][email_address]=jack@example.com' \
>  -F 'signers[0][name]=Jack' \
>  -F 'signers[0][order]=0' \
>  -F 'signers[1][email_address]=jill@example.com' \
>  -F 'signers[1][name]=Jill' \
>  -F 'signers[1][order]=1' \
>  -F 'cc_email_addresses[]=lawyer1@dropboxsign.com' \
>  -F 'cc_email_addresses[]=lawyer2@dropboxsign.com' \
>  -F 'metadata[custom_id]=1234' \
>  -F 'metadata[custom_text]=NDA #9' \
>  -F 'signing_options[draw]=1' \
>  -F 'signing_options[type]=1' \
>  -F 'signing_options[upload]=1' \
>  -F 'signing_options[phone]=1' \
>  -F 'signing_options[default_type]=draw' \
>  -F 'signing_options[force_advanced_signature_details]=0' \
>  -F 'field_options[date_format]=DD - MM - YYYY' \
>  -F 'test_mode=1'
1{
2  "signature_request": {
3    "test_mode": true,
4    "signature_request_id": "2b388914e3ae3b738bd4e2ee2850c677e6dc53d2",
5    "requester_email_address": "me@dropboxsign.com",
6    "title": "NDA with Acme Co.",
7    "original_title": "The NDA we talked about",
8    "subject": "The NDA we talked about",
9    "message": "Please sign this NDA and then we can discuss more. Let me know if you have any questions.",
10    "metadata": {
11      "custom_id": "1234",
12      "custom_text": "NDA #9"
13    },
14    "created_at": 1570471067,
15    "is_complete": false,
16    "is_declined": false,
17    "has_error": false,
18    "files_url": "https://api.hellosign.com/v3/signature_request/files/2b388914e3ae3b738bd4e2ee2850c677e6dc53d2",
19    "signing_url": "https://app.hellosign.com/sign/2b388914e3ae3b738bd4e2ee2850c677e6dc53d2",
20    "details_url": "https://app.hellosign.com/home/manage?guid=2b388914e3ae3b738bd4e2ee2850c677e6dc53d2",
21    "cc_email_addresses": [
22      "lawyer1@dropboxsign.com",
23      "lawyer2@example.com"
24    ],
25    "signing_redirect_url": null,
26    "template_ids": null,
27    "custom_fields": [],
28    "attachments": [
29      {
30        "id": "id_1",
31        "signer": "1",
32        "name": "Attachment #1",
33        "required": true,
34        "instructions": "Instructions #1",
35        "uploaded_at": 1650398513
36      },
37      {
38        "id": "id_2",
39        "signer": "2",
40        "name": "Attachment #2",
41        "required": true,
42        "instructions": null,
43        "uploaded_at": null
44      }
45    ],
46    "response_data": [],
47    "signatures": [
48      {
49        "signature_id": "78caf2a1d01cd39cea2bc1cbb340dac3",
50        "signer_email_address": "jack@example.com",
51        "signer_name": "Jack",
52        "signer_role": null,
53        "order": 0,
54        "status_code": "awaiting_signature",
55        "signed_at": null,
56        "last_viewed_at": null,
57        "last_reminded_at": null,
58        "has_pin": false,
59        "has_sms_auth": false
60      },
61      {
62        "signature_id": "616629ed37f8588d28600be17ab5d6b7",
63        "signer_email_address": "jill@example.com",
64        "signer_name": "Jill",
65        "signer_role": null,
66        "order": 1,
67        "status_code": "awaiting_signature",
68        "signed_at": null,
69        "last_viewed_at": null,
70        "last_reminded_at": null,
71        "has_pin": false,
72        "has_sms_auth": false
73      }
74    ]
75  }
76}

Creates and sends a new SignatureRequest with the submitted documents. If form_fields_per_document is not specified, a signature page will be affixed where all signers will be required to add their signature, signifying their agreement to all contained documents.

Was this page helpful?
Previous

Download Files as File Url

Next

Send with Template

Built with

Authentication

AuthorizationBasic

Your API key can be used to make calls to the Dropbox Sign API. See Authentication for more information. ✅ Supported by Try it console (calls sent in test_mode only).

OR
AuthorizationBearer
You can use an Access Token issued through an OAuth flow to send calls to the Dropbox Sign API from your app. The access scopes required by this endpoint are listed in the gray box above. See [Authentication](/api/reference/authentication) for more information. ❌ **Not supported** by Try it console.

Request

This endpoint expects an object.
fileslist of stringsOptional

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

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

file_urlslist of stringsOptional

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.

signerslist of objectsOptional

Add Signers to your Signature Request.

This endpoint requires either signers or grouped_signers, but not both.

grouped_signerslist of objectsOptional

Add Grouped Signers to your Signature Request.

This endpoint requires either signers or grouped_signers, but not both.

allow_declinebooleanOptionalDefaults to false

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

allow_reassignbooleanOptionalDefaults 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.

attachmentslist of objectsOptional
A list describing the attachments
cc_email_addresseslist of stringsOptional
The email addresses that should be CCed.
client_idstringOptional
The client id of the API App you want to associate with this request. Used to apply the branding and callback url defined for the app.
custom_fieldslist of objectsOptional

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.

field_optionsobjectOptional
This allows the requester to specify field options for a signature request.
form_field_groupslist of objectsOptional

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.

form_field_ruleslist of objectsOptional

Conditional Logic rules for fields defined in form_fields_per_document.

form_fields_per_documentlist of objectsOptional

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
Variant:
hide_text_tagsbooleanOptionalDefaults to false

Enables automatic Text Tag removal when set to true.

NOTE: Removing text tags this way can cause unwanted clipping. We recommend leaving this setting on false and instead hiding your text tags using white text or a similar approach. See the Text Tags Walkthrough for more information.

is_eidbooleanOptionalDefaults to false

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.
NOTE: You need the eID add-on to use this feature. Please contact sales for more information. Cannot be used in test_mode. Only works on requests with one signer.

messagestringOptional<=5000 characters
The custom message in the email that will be sent to the signers.
metadatamap from strings to anyOptional

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_optionsobjectOptional

This allows the requester to specify the types allowed for creating a signature and specify another signing options.

NOTE: If signing_options are not defined in the request, the allowed types will default to those specified in the account settings.

NOTE: If force_advanced_signature_details is set, allowed types has to be defined too.

signing_redirect_urlstringOptional
The URL you want signers redirected to after they successfully sign.
subjectstringOptional<=255 characters
The subject in the email that will be sent to the signers.
test_modebooleanOptionalDefaults to false

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

titlestringOptional<=255 characters
The title you want to assign to the SignatureRequest.
use_text_tagsbooleanOptionalDefaults to false

Send with a value of true if you wish to enable Text Tags parsing in your document. Defaults to disabled, or false.

expires_atinteger or nullOptional

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.

Response headers

X-RateLimit-Limitinteger
The maximum number of requests per hour that you can make.
X-RateLimit-Remaininginteger
The number of requests remaining in the current rate limit window.
X-Ratelimit-Resetinteger
The Unix time at which the rate limit will reset to its maximum.

Response

successful operation
signature_requestobject
Contains information about a signature request.
warningslist of objects
A list of warnings.

Errors

4XX
Client Request Error

You can use an Access Token issued through an OAuth flow to send calls to the Dropbox Sign API from your app. The access scopes required by this endpoint are listed in the gray box above. See Authentication for more information. ❌ Not supported by Try it console.