Bulk-send a Dropbox Sign template to multiple signers using a CSV recipient list
domain: developers.hellosign.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Prepare a CSV file with one row per signer; include columns for the signer name, email_address, and any custom fields (suffixed with _field as required by the Dropbox Sign CSV format)
POST to /signature_request/bulk_send_with_template with template_ids (one or more template IDs), the CSV file as the signer_file parameter, and your subject and message
The response contains a bulk_send_job_id and the total count of signature requests being created (up to 250 per call)
Poll GET /bulk_send_job/{bulk_send_job_id} to track job_total, total_sent, and total_error counts
Retrieve individual signature request details from the job results to identify any failed sends; fix recipient data and re-submit failed rows
Known gotchas
Bulk send with template is limited to Standard plan and higher; the endpoint returns an error on lower-tier API keys
Each bulk send job creates up to 250 signature requests; split larger lists into batches of 250 and submit sequentially
When using multiple templates in one bulk send, no more than one of the templates may have ordered signers; mixing multiple ordered-signer templates is not supported
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?