Niches · Contracts, proposals & e-signatures
Send a saved template for signature with fields pre-filled
Four or more companies' docs show a full fit.
What counts as done
One signature request created from the template with every pre-filled value visible on the document sent and each signer's name and email correct, with the request id returned.
Measured, for our own tests: in at most two calls. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: send the NDA template to this person
, send our contractor agreement to Mary for signature
, fill in the company name and send it out
, create the contract from our template for this client
Does the job 4
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| BoldSign BB Syncfusion, Inc. | POST /v1/template/send takes the template id and Roles (RoleIndex, signer name, email, SignerOrder, SignerType) with ExistingFormFields to set values on template fields, and returns the documentId in one call. source |
| DocuSeal B DocuSeal, LLC | POST /submissions takes template_id, submitters with role, name and email, and submitters.values or fields.default_value (readonly optional) to prefill. One call returns submission and submitter ids with status sent. source |
| Dropbox Sign B Dropbox, Inc. | POST /signature_request/send_with_template takes template_ids, signers by role with name and email, custom_fields with name and value, and metadata, and returns the signature_request_id in one call. Available from the Essentials plan. source |
| SignWell B Docsketch, LLC (DBA SignWell) | POST /api/v1/document_templates/documents takes template_id, recipients mapped to placeholders with name and email, and template_fields by api_id and value, sends in the same call unless draft is true, and returns the document id. source |
Does the job, with a limit 6
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Adobe Acrobat Sign D Adobe Inc. | POST /agreements takes a libraryDocumentId in fileInfos, participantSetsInfo, mergeFieldInfo defaults and state IN_PROCESS, one call. The only field reference readable is the obsolete SDK's model docs (the REST reference host bars bots), and acc-28 saw a field lose its date format. source |
| Documenso C Documenso, Inc. | POST /envelope/use takes the template envelopeId, recipients by template id with email and name, prefillFields with values, externalId and distributeDocument=true, so one call sends. acc-13 got six consecutive 429s from /envelope/use on Teams, still open. source |
| Docusign B Docusign, Inc. | Envelopes:create takes templateId, templateRoles with roleName, name, email and tabs, status sent and transactionId, one call. acc-17, acc-20 and acc-21 had sender values arrive blank: a demo template without prefill permission, ignored DocGen values and prefill tabs under composite templates. source |
| PandaDoc B PandaDoc | Create document from a template takes recipients by role, tokens and fields to prefill, but creation is asynchronous: the agent must wait for document.draft (a 404 before it) and then call send, so at least three calls. Each production create uses a usage credit. source |
| airSlate SignNow B airSlate, Inc. | POST /template/{id}/copy makes the document, PUT /v2/documents/{id}/prefill-texts writes sender values and POST /document/{id}/invite sends by role and email: three calls, one over the success criterion. Each repeated invite is charged. source |
| Youtrust BB Youtrust SAS | POST /signature_requests with template_id and template_placeholders (signers and read_only_text_fields), then /activate: two calls, ids returned. The pricing matrix marks Templates unavailable in the 40-day sandbox, so the flow can't be built before buying a plan. source |
What stops agents finishing
- template built in an account that lacks prefill permission, so values arrive blank
- fair-use or plan rate limit hit by a batch of sends
- MCP connector cannot authenticate the agent
Around it
Before: crm.find-deal, e-signatures.generate-and-send. After: e-signatures.track-status.
Where this comes from
Weight 32 of 100 in Contracts, proposals & e-signatures: 11 of 31 accounts; the job behind the Docusign MCP thread, the Documenso 429 and prefill issues, the SignWell MCP name bug and most template Stack Overflow questions
The same as data: /api/v1/use-cases/e-signatures.send-from-template.json, or the MCP tool get_use_case with id e-signatures.send-from-template. Other jobs in this category: /api/v1/niches?category=e-signatures.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.