Create and send a document for signature from a template via the Zoho Sign API
domain: sign.zoho.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
First retrieve the template's details via the get-template-details call to obtain each recipient's action_id and any prefillable field_data definitions.
Call the create-document-from-template endpoint with header Authorization: Zoho-oauthtoken <token> and a form field data containing JSON with request_name, field_data (text/boolean/date values), and actions (one entry per recipient with action_id, action_type SIGN, recipient_name, recipient_email, verify_recipient, verification_type).
Set is_quicksend to true to send immediately, or false to create a draft so you can attach an additional document via the update-document endpoint before sending with the separate submit API.
The number of actions (recipients) is fixed by the template — you populate the existing recipient slots but cannot add or remove signers via this call.
Inspect the response's request_status and request_id to confirm the document was created/sent.
Known gotchas
Recipient count is locked to the template definition — this endpoint fills in existing action slots, it does not let you add or remove signers.
Fields marked mandatory in the template must have a value in field_data, or the call fails.
The public API root is sign.zoho.com/api/v1 — not the marketing/docs site at www.zoho.com/sign; conflating the two 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?