REST API for E-Signature & Document Automation
Embed document signing into any CRM, ERP, or app via REST API or MCP server. Automate signing flows, receive webhooks, and maintain a tamper-proof blockchain audit trail.
What you can build with the Chaindoc e-signature API
Extend your products with document automation, embedded signing, and real-time webhook notifications.
Document creation automation
Generate contracts from templates with merge fields, conditional logic, and multi-party routing via API.
Embedded electronic signature
Add signing inside your app or website — signers complete it without a Chaindoc account.
Workflow automation
Multi-step signing flows with sequential or parallel routing, deadlines, and custom actions per stage.
System integration
Connect any HTTP system — CRM, ERP, internal tools. Webhooks push event notifications to your endpoint.
MCP Server for AI agents
AI agents run the full flow via Model Context Protocol: document creation, signing, and invoice payment.
Build with Chaindoc API
Full REST API and MCP server reference with code samples. Ready-to-use SDKs for Node.js, Python, and PHP.
Why build on the Chaindoc API
Production-grade infrastructure with end-to-end security, high SLA, and configuration depth that fits any existing team workflow.
Documents are encrypted end to end. Access is controlled by API keys that you can scope and rotate. Every signature event is logged on the blockchain, creating a tamper-proof audit trail. The platform satisfies the ESIGN Act (US), eIDAS (EU), and UETA — which matters when a signed document gets questioned.
The infrastructure is replicated across regions, scales automatically, and has no maintenance windows. Audit logs and documents are stored redundantly. If something breaks on our side, your integration keeps working.
Full REST API with a typed Node.js/TypeScript Server SDK and browser Embed SDK. Webhooks cover supported lifecycle events, staging is available for development, and the documentation includes working examples. You can start sending real API calls in under an hour.
Customize signing messages, document templates, and the signer interface. Light and dark themes, custom domains, branded email notifications, and configurable role permissions let you match the API to your product's look and feel.
How to integrate the e-signature API
Three steps to get from signup to your first e-signature API call.
Create an account
Sign up or log in to Chaindoc. API keys are generated from the Settings → API section for accounts with API access enabled.
Generate an API key
Create an API key from the Settings panel and store it securely. This key authenticates every request your application makes to Chaindoc. Keep separate staging and production keys.
Make your first API call
Use the REST endpoints directly or install the Node.js/TypeScript Server SDK. The documentation covers every endpoint with working code examples, including a complete webhook setup walkthrough.
Chaindoc + Pipedrive
Sign documents and collect e-signatures directly from Pipedrive deals. Contract status syncs back automatically — no switching tabs, no copy-paste.
- Sign deals and contracts without leaving Pipedrive
- Automatic document status sync
- Blockchain-verified signatures
Start integrating the e-signature API today
Connect the Chaindoc API to your application and automate document creation, signing, and management. First API call in under an hour.
Common questions about the Chaindoc API
Key answers about API integration, authentication, webhooks, and SDK usage. More details on our support page.
The Chaindoc API is a REST interface for managing documents, templates, signers, and signature statuses from your own application. You get endpoints for creating and editing files, launching signing flows, receiving webhooks, and monitoring the audit log. The API uses bearer token authentication and supports role-based access control. See pricing for API access details.
Yes. Every signature created through the Chaindoc API is recorded with a cryptographic timestamp on the blockchain. The platform provides end-to-end encryption, certificates of completion, and a full audit log that satisfies the ESIGN Act (US), eIDAS (EU), and UETA. You can export an evidence package at any time for legal proceedings or internal audits.
SaaS teams, fintechs, insurance companies, legal consultants, and development studios all use the API for different things. Common use cases: automating contracts, client onboarding, internal approvals, and mass document creation. If your product has any kind of agreement flow, the API adds signing without requiring you to rebuild what you already have. Developers building integrations for clients can also join the partner program for dedicated support and custom API pricing.
Yes. Use the staging environment while you build, with API keys created from your Chaindoc account. Test the full happy path there before switching the SDK environment to production.
The Chaindoc API uses bearer token authentication. Every request must include an Authorization header with your API key. Keys can be scoped with read-only or write permissions and rotated from the Settings panel at any time. Use separate staging and production keys so test traffic never touches live data.
Chaindoc webhooks cover document, signature request, contract, invoice, and transaction lifecycle events. Use them for completion, rejection, signing, verification, and payment automation.
Tips for secure integration of e-signature APIs
Learn how to properly and securely use electronic signatures through the Chaindoc API to keep your documents legally valid and audit-ready.
PandaDoc Alternatives: 7 Options Compared on Real Pricing
PandaDoc alternatives compared on pricing taken from each vendor's own page. Per-seat vs unlimited-user models, what a 3- and 10-person team actually pays.
Sanctions Screening: Who Must Do It, and When It Has to Run
Sanctions screening is not an AML-only duty. Every business is barred from dealing with listed parties. What you check, how often, and where it belongs.
Politically Exposed Person: Who Counts, and What Changes When One Signs
A politically exposed person is a client who holds or held prominent public office. Who counts, how long the status lasts, and what you must do differently.