Build a template in the DocuSign web console, defining roles (not specific recipients), tabs (fields), and any locked or pre-filled values; note the resulting templateId.
Construct an envelope creation request using the 'templateRoles' array instead of 'recipients'; supply each role's name, email, and roleName, plus a 'tabs' object to pre-populate text tabs with dynamic data.
POST to /v2.1/accounts/{accountId}/envelopes with status='sent' to dispatch immediately, or status='created' to hold as a draft for review.
To send in bulk, use the BulkSend API: create a bulk send list with recipient data, then POST to /v2.1/accounts/{accountId}/bulk_send_lists/{bulkSendListId}/send referencing the template-based envelope definition.
Monitor bulk send job status via GET /v2.1/accounts/{accountId}/bulk_send_batch/{batchId} until batchStatus is 'completed' or 'failed'.
Retrieve completed documents with GET /v2.1/accounts/{accountId}/envelopes/{envelopeId}/documents/combined to obtain a merged PDF with certificate of completion.
Known gotchas
Bulk send jobs are asynchronous; do not poll in a tight loop — use exponential backoff or a Connect webhook on the envelope-sent event.
Tab labels in pre-population must exactly match the tab label defined on the template; a mismatch silently skips the pre-fill without error.
Bulk send requires a separate DocuSign feature entitlement; verify it is enabled on the account before building the integration.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp