Dropbox Sign Developer Documentation

Creates BulkSendJob which sends up to 250 SignatureRequests in bulk based off of the provided Template(s) specified with the template_ids parameter to be signed in an embedded iFrame. These embedded signature requests can only be signed in embedded iFrames whereas normal signature requests can only be signed on Dropbox Sign.

NOTE: Only available for Standard plan and higher.

Creates BulkSendJob which sends up to 250 SignatureRequests in bulk based off of the provided Template(s) specified with the `template_ids` parameter to be signed in an embedded iFrame. These embedded signature requests can only be signed in embedded iFrames whereas normal signature requests can only be signed on Dropbox Sign. **NOTE:** Only available for Standard plan and higher.

Authentication

AuthorizationBasic

Basic authentication of the form Basic <username:password>.

AuthorizationBearer

Bearer authentication of the form Bearer <token>, where token is your auth token.

Request

This endpoint expects an object.

template_idslist of stringsRequired

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

client_idstringRequired

Client id of the app you're using to create this embedded signature request. Used for security purposes.

signer_filestringOptionalformat: "binary"

signer_file is a CSV file defining values and options for signer fields. Required unless a signer_list is used, you may not use both. The CSV can have the following columns:

name: the name of the signer filling the role of RoleName
email_address: email address of the signer filling the role of RoleName
pin: the 4- to 12-character access code that will secure this signer’s signature page (optional)
sms_phone_number: An E.164 formatted phone number that will receive a code via SMS to access this signer’s signature page. (optional)

By using the feature, you agree you are responsible for obtaining a signer’s consent to receive text messages from Dropbox Sign related to this signature request and confirm you have obtained such consent from all signers prior to enabling SMS delivery for this signature request. Learn more.

NOTE: Not available in test mode and requires a Standard plan or higher.
*_field: any column with a _field” suffix will be treated as a custom field (optional)

You may only specify field values here, any other options should be set in the custom_fields request parameter.

Example CSV:

name, email_address, pin, company_field
George, george@example.com, d79a3td, ABC Corp
Mary, mary@example.com, gd9as5b, 123 LLC

`signer_file` is a CSV file defining values and options for signer fields. Required unless a `signer_list` is used, you may not use both. The CSV can have the following columns: - `name`: the name of the signer filling the role of RoleName - `email_address`: email address of the signer filling the role of RoleName - `pin`: the 4- to 12-character access code that will secure this signer's signature page (optional) - `sms_phone_number`: An E.164 formatted phone number that will receive a code via SMS to access this signer's signature page. (optional) By using the feature, you agree you are responsible for obtaining a signer's consent to receive text messages from Dropbox Sign related to this signature request and confirm you have obtained such consent from all signers prior to enabling SMS delivery for this signature request. [Learn more](https://faq.hellosign.com/hc/en-us/articles/15815316468877-Dropbox-Sign-SMS-tools-add-on). **NOTE:** Not available in test mode and requires a Standard plan or higher. - `*_field`: any column with a _field" suffix will be treated as a custom field (optional) You may only specify field values here, any other options should be set in the custom_fields request parameter. Example CSV: ``` name, email_address, pin, company_field George, george@example.com, d79a3td, ABC Corp Mary, mary@example.com, gd9as5b, 123 LLC ```

signer_listlist of objectsOptional

signer_list is an array defining values and options for signer fields. Required unless a signer_file is used, you may not use both.

allow_declinebooleanOptionalDefaults to false

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

ccslist of objectsOptional

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

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.

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](https://app.hellosign.com/api/textTagsWalkthrough#TextTagIntro) 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](/api/reference/operation/templateCreateEmbeddedDraft) and then passing `custom_fields` on subsequent signature requests referencing that template.

messagestringOptional<=5000 characters

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

metadatamap from strings to anyOptional

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.

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

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

bulk_send_jobobject

Contains information about the BulkSendJob such as when it was created and how many signature requests are queued.

warningslist of objects or null

A list of warnings.

Errors

signer_file is a CSV file defining values and options for signer fields. Required unless a signer_list is used, you may not use both. The CSV can have the following columns:

name: the name of the signer filling the role of RoleName
email_address: email address of the signer filling the role of RoleName
pin: the 4- to 12-character access code that will secure this signer’s signature page (optional)
sms_phone_number: An E.164 formatted phone number that will receive a code via SMS to access this signer’s signature page. (optional)

By using the feature, you agree you are responsible for obtaining a signer’s consent to receive text messages from Dropbox Sign related to this signature request and confirm you have obtained such consent from all signers prior to enabling SMS delivery for this signature request. Learn more.

NOTE: Not available in test mode and requires a Standard plan or higher.
*_field: any column with a _field” suffix will be treated as a custom field (optional)

You may only specify field values here, any other options should be set in the custom_fields request parameter.

Example CSV:

name, email_address, pin, company_field
George, george@example.com, d79a3td, ABC Corp
Mary, mary@example.com, gd9as5b, 123 LLC

1	import json
2	from datetime import date, datetime
3	from pprint import pprint
4
5	from dropbox_sign import ApiClient, ApiException, Configuration, api, models
6
7	configuration = Configuration(
8	username="YOUR_API_KEY",
9	)
10
11	with ApiClient(configuration) as api_client:
12	signer_list_2_custom_fields_1 = models.SubBulkSignerListCustomField(
13	name="company",
14	value="123 LLC",
15	)
16
17	signer_list_2_custom_fields = [
18	signer_list_2_custom_fields_1,
19	]
20
21	signer_list_2_signers_1 = models.SubSignatureRequestTemplateSigner(
22	role="Client",
23	name="Mary",
24	email_address="mary@example.com",
25	pin="gd9as5b",
26	)
27
28	signer_list_2_signers = [
29	signer_list_2_signers_1,
30	]
31
32	signer_list_1_custom_fields_1 = models.SubBulkSignerListCustomField(
33	name="company",
34	value="ABC Corp",
35	)
36
37	signer_list_1_custom_fields = [
38	signer_list_1_custom_fields_1,
39	]
40
41	signer_list_1_signers_1 = models.SubSignatureRequestTemplateSigner(
42	role="Client",
43	name="George",
44	email_address="george@example.com",
45	pin="d79a3td",
46	)
47
48	signer_list_1_signers = [
49	signer_list_1_signers_1,
50	]
51
52	signer_list_1 = models.SubBulkSignerList(
53	custom_fields=signer_list_1_custom_fields,
54	signers=signer_list_1_signers,
55	)
56
57	signer_list_2 = models.SubBulkSignerList(
58	custom_fields=signer_list_2_custom_fields,
59	signers=signer_list_2_signers,
60	)
61
62	signer_list = [
63	signer_list_1,
64	signer_list_2,
65	]
66
67	ccs_1 = models.SubCC(
68	role="Accounting",
69	email_address="accounting@example.com",
70	)
71
72	ccs = [
73	ccs_1,
74	]
75
76	signature_request_bulk_create_embedded_with_template_request = models.SignatureRequestBulkCreateEmbeddedWithTemplateRequest(
77	client_id="1a659d9ad95bccd307ecad78d72192f8",
78	template_ids=[
79	"c26b8a16784a872da37ea946b9ddec7c1e11dff6",
80	],
81	message="Glad we could come to an agreement.",
82	subject="Purchase Order",
83	test_mode=True,
84	signer_list=signer_list,
85	ccs=ccs,
86	)
87
88	try:
89	response = api.SignatureRequestApi(api_client).signature_request_bulk_create_embedded_with_template(
90	signature_request_bulk_create_embedded_with_template_request=signature_request_bulk_create_embedded_with_template_request,
91	)
92
93	pprint(response)
94	except ApiException as e:
95	print("Exception when calling SignatureRequestApi#signature_request_bulk_create_embedded_with_template: %s\n" % e)

1	{
2	"bulk_send_job": {
3	"bulk_send_job_id": "ccaf88244ef006b6e31ebba5ed4cb53b3131d9ac",
4	"total": 3,
5	"is_creator": true,
6	"created_at": 1543556038
7	}
8	}