Your signer doesn't always check email.

Collect money in the same link they sign with.

Connect your Stripe account once. Then any document you send can collect a payment, before they can sign or right after they do. Money lands in your Stripe, not ours. Same 25 cents a document.

• After signing. They sign, and the payment link follows on its own, by the same text or email.
• Before signing. They see the document, pay, and the signing link unlocks.
• Your Stripe, your money. No fee from us on top of Stripe's card fees. A document held for payment isn't billed until it goes out.

Get the ID and the signature in the same link.

Ask for up to five files with any document: a photo ID, proof of insurance, a W-9. Your signer snaps a photo on their phone and it uploads. Want them before the signature? The signing link waits until the files are in.

• Before signing. No files, no signing link.
• After signing. They sign, then the upload link follows on its own.
• Photos from any phone. Shrunk on the phone before upload, so even a big one goes up in seconds.

Files stay with the document; you download them from your Sent list. Nothing is emailed. Ask for a payment on the same document and it's one link, one page: signature, payment and paperwork, not three.

Get the answers and the signature in the same link.

Ask for the policy number, the date of birth, the spouse’s name. They answer on their phone before they sign, and every answer is printed on the document and sent back to you.

• Text, dropdowns, checkboxes and choices. Phone, email and date formats are checked as they type.
• Rules. Ask for the spouse’s name only when they pick Married. Required answers have to be in before they can sign.
• Answers back as data. View answers in the studio, or JSON in your webhook.

Data collection is an Enterprise feature. Everything else stays 25 cents a document.

The e-signature API: tag a PDF, POST it, get a webhook.

You build the PDF and drop anchor tags where the fields go: ^S1 for the signature, ^D1 for the date. White text on a white background, so the tags are invisible to the reader and still sitting in the text layer where we can find them.

Post the file with your signer details. We deliver by email, SMS, or both in parallel, and fire a webhook when it's signed. Download the signed document there and keep your own copy.

No drag-and-drop field editor. No coordinate maps. Templates if you want them, never required. One endpoint and a PDF you already know how to generate. There's no sales call between you and a sent document, and the first send is minutes of work, not an afternoon.

Send your first document in about two minutes.

Free document signing that works the way your customers already do: you send a document for signature, they open a text or an email, and they sign on their phone from wherever they are.

1. Upload your PDF. Up to 3 MB. If it's in Word or Google Docs, save it as a PDF first.
2. We mark where they sign. The studio reads the labels on your page (Signature, Printed name, Date) and suggests a box for each. One click adds it, one click skips it. Anything it missed, click to place.
3. Send by text, email, or both. Track it from the Sent tab.

Your assistant can send the contract itself.

Add the Siglio MCP server to Claude Desktop, or any MCP client, and ask it to send a document. It sends by text or email, tells you who has signed, downloads the signed copy and any files they uploaded, and cancels an envelope if you change your mind. Five tools. Nothing to write.

Paste this into claude_desktop_config.json, restart Claude, and say “send lease.pdf to Jane for signature.”

Your first 25 documents are free and deliver for real, so your first send is a real proof. The server won’t void anything without asking you first. Full setup and what each tool does

A signature is only worth the evidence behind it.

Electronic signatures have carried the same legal force as ink in the United States since 2000, under the federal ESIGN Act and, at state level, the Uniform Electronic Transactions Act. UETA is law in 49 states plus the District of Columbia, Puerto Rico and the U.S. Virgin Islands. New York is the lone holdout and runs its own Electronic Signatures and Records Act instead, which reaches the same result by a different route.

None of that is the interesting part. Neither statute makes a signature valid because a vendor says so. What survives a challenge is the record of what happened, so here is exactly what we record and what we don't.

Docs that answer the question you actually have.

Endpoints, the tag system, delivery options, the complete error table, idempotency semantics, webhook retry behavior, limits, and billing. All of it public, none of it behind a sales call.

Every endpoint has a cURL example. Every error in the reference is one your code can actually receive. And if something in there is unclear or missing, tell support, because that's how the docs get better.