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 in the sandbox.

What SDKs are available for Chaindoc?

Chaindoc has SDKs for JavaScript/TypeScript, Python, and Go. The SDKs and libraries page has installation instructions and code samples. If your language isn't listed, 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 sandbox?

Yes, but it's free. Sign up at chaindoc.io and you'll get sandbox access automatically. No credit card needed. The sandbox mirrors production, so anything you build there will work the same way when you switch.

Where can I find Chaindoc code examples?

Every docs page has inline code snippets. For full working examples, the guides section includes end-to-end signing flows, bulk operations, and template-based workflows with copy-paste code.

Your first signature

This guide walks you through sending your first document for signing in Chaindoc's web interface. The whole process takes about 5 minutes.

If you're looking for the API version of this, check the quick start guide instead — it covers both the UI and the code path. This page is specifically about clicking through the web app.

What you'll need

A Chaindoc account (the free plan works). Sign up here if you haven't.
A document to sign — PDF is best, but Word and image files work too.
The email addresses of whoever needs to sign.

Upload your document

1Go to DocumentsClick "Documents" in the sidebar or on the dashboard.

2Click "New Document"It's in the top right. You can also drag and drop a file directly onto the page.

3Pick your fileSelect a PDF, Word doc, or image (max 50MB). Non-PDF files get converted automatically.

4Fill in the detailsGive it a clear name ("Q4 Consulting Agreement" not "doc_final_v2.pdf"), add a description, and tag it if you want. Set the access level to Private if it's sensitive.

Naming tip

Use names that make sense 6 months from now. "Employment Contract - John Doe - 2025" is easy to find. "Contract" isn't.

Create the signature request

Once the document is uploaded, click "Request Signatures" on the document page. This opens the request builder.

1Add recipientsType in the email addresses of your signers. You can add one or many.

2Pick the signing orderParallel means everyone signs at the same time. Sequential means they go one by one in the order you set. For simple documents, parallel is faster.

3Set a deadlinePick when signatures need to be in by. 7-14 days is typical for most contracts. Chaindoc sends automatic reminders as the deadline gets close.

4Write a messageAdd a note explaining what the signer is looking at. Something like "Please review and sign our Q4 consulting agreement" goes a long way.

Optional settings

Most of the time you won't need these, but they're there:

KYC verification — require identity verification before signing. Only needed for high-security documents.
Custom reminders — change the reminder frequency (default is every 3 days).
Notifications — pick whether signers get email, SMS, or both.
Download access — let signers download the document before signing.

Review and send

You'll see a summary of everything before sending. Double-check the recipient emails and signing order. Typos in email addresses are the number one reason signature requests don't arrive.

Hit "Send Request" and you're done. Each recipient gets an email with a secure signing link.

What your signers see

Understanding the signer's side helps you set up better requests. Here's their flow:

1Email with signing linkThey get an email with a "Review and Sign" button. No Chaindoc account needed.

2Identity checkA one-time code is sent to their email for verification. If KYC is enabled, they'll do identity verification too.

3Document reviewThe document opens in a viewer where they can read through everything, zoom in, and navigate.

4Apply signatureThey can type their name, draw a signature, or upload an image of their handwritten signature.

5DoneThey get a confirmation email with a copy of the signed document.

For more on signature types (simple, advanced, qualified) and what each means for compliance, see the signatures docs.

Track progress

Go back to the document page to see who's signed and who hasn't. You'll see a timeline of every event: when the email was sent, when it was opened, when the signer viewed the document, and when they signed.

If someone is taking too long, you can resend the invitation or send a manual reminder. Automatic reminders go out every 3 days by default.

Download the signed document

Once everyone signs, you'll get a notification. Go to the document page and download:

The signed PDF with all signatures embedded
The blockchain verification certificate (proves the document hasn't been modified)
The full audit trail: timestamps, IP addresses, authentication methods, and device info

The document is now blockchain-verified and legally binding. All parties have copies. The audit trail is preserved permanently.

Common questions

What if a signer doesn't get the email?

Have them check spam/junk first. Corporate email filters sometimes block signing links. If it's not there, verify the email address is correct and resend from the request status page. You can also whitelist chaindoc.io with their IT team.

Can I cancel after sending?

Yes. Open the signature request and click "Cancel". All pending signers get notified that it's been cancelled. Signatures already collected are voided.

What happens when the deadline passes?

The request expires automatically. You can create a new one with a new deadline if you still need the signatures. The old request stays in your history for reference.

Are the signatures legally binding?

Yes. Chaindoc signatures comply with eIDAS (EU), the ESIGN Act, and UETA (US). The blockchain verification adds an extra layer of evidence that can matter in legal disputes. For regulated industries, consider using advanced or qualified signature types.

What to do next

Now that you've sent your first signature, here's where to go depending on what you need:

Signatures — understand the different signature types and when to use each
Document management — folders, permissions, and version control
Team management — invite colleagues and set up roles
API integration — automate this whole flow with code
Security — what to configure for sensitive documents

Documentation