ChaindocLabs
For developers

Chaindoc Labs Documentation

Guides, feature walkthroughs and API references for Chaindoc — the blockchain-powered document signing platform.

Browse the docsOpen source
Topics

Browse the documentation

Get up and running with Getting Started, explore what the platform can do in Features, follow practical Guides, or dive into the API and SDK reference.

Getting StartedFeaturesGuidesReference
Open Source

Open-source SDKs & tools

Official SDKs, an MCP server, and a Claude Code plugin marketplace — everything you need to embed and automate Chaindoc signing.

TypeScript@chaindoc_io/embed-sdk

Embed SDK

Official JavaScript / TypeScript SDK for embedding Chaindoc signature flows into web applications. Modal or inline. Framework-agnostic. Zero runtime dependencies. Type-safe postMessage API.

View on GitHub
TypeScript@chaindoc_io/server-sdk

Server SDK

Server-side SDK for the Chaindoc API. Documents, signatures, contracts, invoicing, embedded sessions, blockchain verification, webhook signature verification. Native fetch, Node 18+, zero dependencies.

View on GitHub
TypeScript@chaindoc_io/mcp-server

MCP Server

Model Context Protocol server for Chaindoc. Lets Claude Desktop, Claude Code, Cursor, and other MCP-aware agents drive the Chaindoc REST API in natural language — create documents, send signature requests, verify on chain.

View on GitHub
MarketplaceChaindocIO/claude-plugins

Claude Plugins

Claude Code plugin marketplace for Chaindoc. Install via /plugin marketplace add ChaindocIO/claude-plugins, then /plugin install chaindoc@chaindoc. Bundles the Chaindoc MCP server and its slash commands.

View on GitHub
FAQ

Docs FAQ

Quick answers to common questions about Chaindoc documentation.

Where do I start with Chaindoc?
Head to the Quick Start guide. It walks you through creating an account, uploading your first document, and sending it for signature. Takes about five minutes if you already have a document ready.
Is there an API reference?
Yes. The API reference covers every endpoint, including authentication, document upload, signer management, and webhook configuration. Each endpoint includes request and response examples you can test against the staging environment.
What SDKs are available for Chaindoc?
Chaindoc has a Server SDK for Node.js/TypeScript and an Embed SDK for browser integration. Check the SDKs and libraries page for installation instructions and code samples. For other languages, the REST API works with any HTTP client.
How do webhooks work in Chaindoc?
Chaindoc sends POST requests to your endpoint when events happen: document signed, viewed, expired, and so on. The webhooks guide shows how to configure endpoints, verify signatures, and handle retries.
Do I need an account to use the Chaindoc staging environment?
Yes. API access requires an account with API keys enabled. Use staging keys while you build, then switch the SDK environment to production for live traffic.
Where can I find Chaindoc code examples?
Every docs page has inline code snippets. For a complete end-to-end example, the quick start guide walks through installing an SDK and sending your first signature request with copy-paste code.