E-Signature
SignWell
API integration
Ship E-Signature features without building the integration. Full SignWell API access via Proxy and 20+ MCP-ready tools for AI agents — extend models and mappings to fit your product.
Talk to usUse Cases
Why integrate with SignWell
Common scenarios for SaaS companies building SignWell integrations for their customers.
Embed e-signatures into HR and ATS workflows
Let HR platforms send offer letters and onboarding documents directly from candidate records, auto-populate templates with candidate data, and sync completed PDFs back to employee profiles without manual uploads.
Power compliant signatures for healthcare and life sciences SaaS
Clinical trial, EHR, and life-sciences platforms can offer FDA 21 CFR Part 11-compliant signing to their customers without building a cryptographic signature engine in-house.
Enable bulk document distribution for PropTech and operations platforms
Property managers and operations teams can send lease addendums, policy updates, or notices to hundreds of recipients via CSV-driven bulk sends initiated inside your SaaS UI.
Accelerate quote-to-cash in CRMs and sales tools
Sales teams can trigger contracts from deal records, deliver signing links via SMS for faster conversion, and fix recipient details on in-flight documents without voiding and restarting.
Support LATAM compliance for cross-border business platforms
B2B SaaS serving Mexican markets can automatically retrieve NOM-151 constancia certificates alongside signed PDFs, giving their customers audit-ready compliance artifacts.
What You Can Build
Ship these features with Truto + SignWell
Concrete product features your team can ship faster by leveraging Truto’s SignWell integration instead of building from scratch.
Template-driven document generation
Map internal records (deals, candidates, tenants) to SignWell template placeholders and create pre-filled documents routed to the right recipients in one API call.
Webhook-based signature status sync
Register SignWell webhooks per tenant to listen for document lifecycle events and update your UI in real time when documents are viewed, signed, or completed.
Completed PDF and audit artifact storage
Automatically download completed PDFs and NOM-151 certificates once documents are signed and attach them to the originating record in your product.
CSV-validated bulk send campaigns
Let users upload a recipient CSV, validate it row-by-row with pre-send checks, and launch a bulk send against a template — all inside your app.
In-flight document corrections and reminders
Allow users to update recipient emails or phone numbers on sent documents, enforce passcode authentication for sensitive contracts, and send reminders without canceling the document.
SMS and email omnichannel delivery
Expose a delivery-channel toggle so your users can send signature requests via email, SMS, or both to maximize completion rates.
SuperAI
SignWell AI agent tools
Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.
create_a_sign_well_document
Create a SignWell document and optionally send it for signing; recipients are notified by email, SMS, or both based on delivery_method. Provide the files as the files array (one or more files, each with file_url or file_base64, which accepts base64 content or an uploaded file id) or, for a single file, as top-level file_name + file_base64. Set draft to true to create without sending (send later with documents send; the document needs fields or text tags to be sent); set expires_in to 365 or less and provide phone_number in E.164 format for SMS recipients. Returns: cfr_part11, test_mode, id, name, subject, and 37 more. Required: recipients, plus a file via files or file_name + file_base64.
get_single_sign_well_document_by_id
Get a SignWell document with all associated data by id; supply the unique document ID from a creation request or Document page URL. Returns: cfr_part11, cfr_part11_signing_mode, test_mode, id, name, subject, message, metadata, created_at, updated_at, recipients, status, files, fields, allow_decline, allow_reassign, and 26 more. Required: id.
delete_a_sign_well_document_by_id
Delete a SignWell document by id; deleting also cancels document signing if it is in progress. Returns an empty 204 response on success. Required: id.
sign_well_documents_send
Update a draft SignWell document and send it to its recipients for signing. Returns: cfr_part11, test_mode, id, subject, message, updated_at, recipients, status, files, fields, allow_decline, allow_reassign, and 30 more. subject and message apply to email notifications only; SMS notifications use fixed system templates. Required: document_id.
create_a_sign_well_document_templates_document
Create a SignWell document from one or more templates and optionally send it for signature; pre-signed template signatures and initials copy over as visible content without generating signing events. Returns: cfr_part11, cfr_part11_signing_mode, test_mode, id, template_ids, name, recipients, status, files, fields, and 32 more. Required: recipients.
sign_well_document_recipients_bulk_update
Update one or more recipients on a sent SignWell document; only recipients who have not started signing can be changed, and only while the document is in sent, viewed, pending, or bounced status. Returns the updated document with id, status, and its recipients (id, name, email, signing_url). Required: document_id, recipients.
sign_well_document_authentications_bulk_update
Update passcode delivery settings for recipients on a sent SignWell document; only recipients who have not started signing can be updated. Returns the updated document object including id, status, recipients, and updated_at. Required: document_id, recipients.
create_a_sign_well_document_remind
Send a reminder to SignWell document recipients who have not signed yet, delivered via each recipient's method (email, SMS, or both). Returns the updated document object including id, status, recipients with signing_url, and subject. Required: document_id.
get_single_sign_well_document_completed_pdf_by_id
Download the completed PDF or ZIP file for a signed Signwell document. Returns file_url in a JSON object when url_only=true, otherwise streams the raw PDF or ZIP binary. zip is unavailable on 21 CFR Part 11 documents. Required: id.
create_a_sign_well_document_template
Create a new reusable SignWell document template. Provide the files as the files array (one or more files, each with exactly one of file_url or file_base64, which accepts base64 content or an uploaded file id) or, for a single file, as top-level file_name + file_base64; at least one placeholder should be left unassigned. Returns the created template including id, name, status, created_at, fields, placeholders, and files. Required: placeholders, plus a file via files or file_name + file_base64.
get_single_sign_well_document_template_by_id
Get a SignWell document template by id, including all associated template data. Returns: id, api_application_id, requester_email_address, custom_requester_name, custom_requester_email, name, subject, message, metadata, created_at, updated_at, placeholders, copied_placeholders, status, reminders, archived, files, fields, and 13 more. Required: id.
update_a_sign_well_document_template_by_id
Update an existing SignWell document template by id. Returns the updated template including id, name, status, fields, placeholders, and updated_at. Required: id.
delete_a_sign_well_document_template_by_id
Delete a SignWell document template by id. Returns an empty 204 response on success. Required: id.
get_single_sign_well_api_application_by_id
Get a specific SignWell API Application by id. Returns: id, name, callback_urls, created_at, updated_at, owner, preferences. Required: id.
delete_a_sign_well_api_application_by_id
Delete a SignWell API Application by id. Returns an empty 204 response on success. Required: id.
list_all_sign_well_hooks
List all webhooks registered in your SignWell account. Returns: id, callback_url, api_application_id.
create_a_sign_well_hook
Register a SignWell webhook to receive document lifecycle events at a callback URL. Returns the created webhook with id, callback_url, and api_application_id. Required: callback_url. A document_signed event is not emitted when a pre-signed template signature/initials was merely copied as document content.
delete_a_sign_well_hook_by_id
Delete a registered SignWell webhook by id so document events stop being posted to its callback URL. Returns an empty 204 response on success. Required: id.
list_all_sign_well_me
Retrieve the SignWell account information associated with the authenticated API key, including the credential record, user, account, workspace, and contact. Returns: id, role, archived, user, account, workspace, contact. Takes no parameters.
get_single_sign_well_bulk_send_by_id
Get a SignWell bulk send by id. Returns: id, name, api_application_id, documents_count, documents_completed, documents_not_completed, created_at, user_id, status, templates. Required: id.
list_all_sign_well_bulk_sends
List SignWell bulk sends. Returns: id, name, api_application_id, documents_count, documents_completed, documents_not_completed, created_at, user_id, status, template_ids. Optional filters: user_email, api_application_id.
create_a_sign_well_bulk_send
Create a SignWell bulk send that sends a template to multiple recipients from CSV data; the CSV is validated before the send is enqueued (invalid rows return a 422). Returns: id, template_ids, api_application_id, documents_count, created_at, user_id, status. Required: template_ids, bulk_send_csv.
list_all_sign_well_bulk_sends_csv_templates
Get the SignWell Bulk Send CSV template for one or more document templates: a blank CSV whose columns hold the required and optional recipient data for a bulk send, named [placeholder]_[field label] (e.g. signer_company_name). Returns the base64-encoded CSV in data. Required: template_ids[].
create_a_sign_well_bulk_sends_validate_csv
Validate a SignWell bulk send CSV, checking its structure and row data before creating the bulk send. Returns the validated CSV configuration with defaults applied: bulk_send_csv, template_ids, skip_row_errors, name, subject, message. Invalid CSVs return 422 row-level errors. Required: template_ids, bulk_send_csv.
list_all_sign_well_bulk_send_documents
List the SignWell documents generated for a bulk send. Returns each document's id, name, status, recipients, files, and created_at. Required: bulk_send_id.
get_single_sign_well_document_nom_151_certificate_by_id
Download the NOM-151 certificate for a completed SignWell document by id. By default returns the certificate ZIP file; with url_only=true returns JSON with file_url; with object_only=true returns the raw constancia certificate object as JSON. Required: id. Only succeeds when a NOM-151 certificate is available for the document.
Why Truto
Why use Truto’s MCP server for SignWell
Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 850+ integrations.
Auto-generated, always up to date
Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.
Fine-grained access control
Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.
Multi-tenant by design
Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.
Works with every MCP client
Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.
Built-in auth, rate limits, and error handling
Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.
Expiring and auditable servers
Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.
How It Works
From zero to integrated
Go live with SignWell in under an hour. No boilerplate, no maintenance burden.
Link your customer’s SignWell account
Use Truto’s frontend SDK to connect your customer’s SignWell account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.
We handle authentication
Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.
Call our API, we call SignWell
Truto’s Proxy API is a 1-to-1 mapping of the SignWell API. You call us, we call SignWell, and pass the response back in the same cycle.
Unified response format
Every response follows a single format across all integrations. We translate SignWell’s pagination into unified cursor-based pagination. Data is always in the result attribute.
FAQs
Common questions about SignWell on Truto
Authentication, rate limits, data freshness, and everything else you need to know before you integrate.
How does authentication work for SignWell via Truto?
Your end users connect their own SignWell account through Truto's auth flow. Truto manages credential storage, refresh, and per-tenant isolation so you never handle SignWell API keys directly.
Which SignWell operations are available through Truto?
Truto exposes document create/send/get/delete, template management, bulk sends with CSV validation, recipient and authentication bulk updates, reminders, webhooks, completed PDF retrieval, and NOM-151 certificate downloads.
Can we listen to SignWell events in real time?
Yes. You can create and manage SignWell webhooks per connected account through Truto, so your product receives document lifecycle events (sent, viewed, signed, completed) as they happen.
Does Truto support SignWell's bulk send workflow end-to-end?
Yes. You can fetch CSV templates, validate CSVs before dispatch, create bulk sends, and list the resulting documents — enabling you to build a full bulk-send UI inside your product.
Can we support compliance use cases like FDA 21 CFR Part 11 or NOM-151?
Yes. Documents can be created with CFR Part 11 flags for FDA-regulated signing, and NOM-151 certificates can be retrieved per document for customers operating in Mexico.
Can users correct recipient details after a document is sent?
Yes. Truto exposes SignWell's bulk recipient update and authentication update endpoints, so you can fix emails, phone numbers, or add passcodes on documents that are still in sent, viewed, pending, or bounced states.
Is this integration already live or built on request?
SignWell is available in Truto's catalog with the listed tools. If you need additional endpoints or a unified e-signature API layer on top, Truto can scope and ship those on request.
From the Blog
SignWell integration guides
Deep dives, architecture guides, and practical tutorials for building SignWell integrations.
SignWell
Get SignWell integrated into your app
Our team understands what it takes to make a SignWell integration successful. A short, crisp 30 minute call with folks who understand the problem.