Send multiple related SignNow documents as a single signing transaction using document groups / grouped templates
domain: docs.signnow.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Prepare source documents: convert any templates to documents first via the template-copy endpoint; each document must be owned by the caller, must not itself be a template, and must not already belong to another group or have active/fulfilled invites.
Create an ad hoc group by calling the document-group create endpoint with a document_ids array and a group_name — returns the document group id.
For a reusable, repeatable multi-document package instead, build a Document Group Template (a separate resource) by adding templates to it, then instantiate a fresh document group from that template for each new transaction.
Send the whole group for signature as one transaction so recipients move through all grouped documents in a single guided signing flow rather than separate individual invites.
Download the completed set — by default as a zip archive of the group; pass a merged type parameter to receive one merged PDF instead.
Known gotchas
At least one document/template in the group must already contain fields, or the group cannot be sent for signature.
A document can belong to only one group at a time; adding a document already in another group or with pending/completed invites will fail.
Document Groups (built ad hoc from specific document IDs) and Document Group Templates (reusable across many transactions) are separate resources with separate endpoints — conflating them is a common integration mistake.
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?