# Sigil Documentation

> Sigil is an e-signature service: upload a PDF or Word document with glyphs (short typed codes) marking where people sign, send it to them in order as a pact, and get back a stamped PDF sealed with its sigil, a certificate of completion. These docs cover its REST API (https://api.signwithsigil.com/v1) and its hosted MCP server (https://api.signwithsigil.com/mcp).

Every page is also available as Markdown: add `.md` to its URL (the home page is https://docs.signwithsigil.com/index.md). Everything in one file: https://docs.signwithsigil.com/llms-full.txt

## Guides

- [Introduction](https://docs.signwithsigil.com/index.md): Send documents for signature from your own code or from an AI assistant, with the Sigil REST API and MCP server.
- [Quickstart](https://docs.signwithsigil.com/quickstart.md): Upload a document with glyphs, send it to two signers, follow their progress and download the signed PDF.
- [Authentication](https://docs.signwithsigil.com/authentication.md): Create API keys on the dashboard and send one with every request. The same key works for the REST API and the MCP server.
- [Errors](https://docs.signwithsigil.com/errors.md): Every error is a JSON object with one message, written so you can show it to a person. These are the status codes and what to do about each.
- [Glyphs](https://docs.signwithsigil.com/concepts/glyphs.md): Fields come from glyphs, short codes typed into the document, like \s1\ for signer 1's signature, so the same file works every time.
- [Pact lifecycle](https://docs.signwithsigil.com/concepts/pacts.md): How a pact moves from draft to sealed, how signers take turns, what signing links are, and how to follow progress.
- [Documents and plans](https://docs.signwithsigil.com/concepts/documents.md): Sending is metered in documents, one for every three signers. They come from your plan's monthly allowance first, then from packs that never expire.
- [FAQ](https://docs.signwithsigil.com/faq.md): Short answers to common questions about the API and MCP server, and a glossary of Sigil's words (pact, glyph, sigil, sealed, lapsed, void) and where they come from.

## API reference

- [API reference](https://docs.signwithsigil.com/api-reference.md): The Sigil REST API: base URL, request and response conventions, ids, times and paging, and every endpoint at a glance.
- [Get account](https://docs.signwithsigil.com/api-reference/account/get-account.md): The account the key belongs to: its plan, the documents it can still send, and its verified custom domains.
- [List templates](https://docs.signwithsigil.com/api-reference/templates/list-templates.md): Every template you have saved, most recently updated first.
- [Get a template](https://docs.signwithsigil.com/api-reference/templates/get-template.md): One template with every field its glyphs define.
- [Create a template](https://docs.signwithsigil.com/api-reference/templates/create-template.md): Upload a PDF or Word document with glyphs and save it as a template.
- [Delete a template](https://docs.signwithsigil.com/api-reference/templates/delete-template.md): Delete a template. Pacts already made from it keep their own copy of the document.
- [List pacts](https://docs.signwithsigil.com/api-reference/pacts/list-pacts.md): Your pacts, most recently updated first, filtered by status and paged.
- [Get a pact](https://docs.signwithsigil.com/api-reference/pacts/get-pact.md): One pact in full: recipients and their progress, fields with their values, the event log and download links.
- [Create a pact](https://docs.signwithsigil.com/api-reference/pacts/create-pact.md): Create a pact from a template or a one-off file, and optionally send it in the same call.
- [Send a pact](https://docs.signwithsigil.com/api-reference/pacts/send-pact.md): Send a draft: the first signer is emailed a private link, and the pact's documents are charged.
- [Resend the signing link](https://docs.signwithsigil.com/api-reference/pacts/resend-pact.md): Email a fresh link to the signer whose turn it is. Their previous link stops working.
- [Void a pact](https://docs.signwithsigil.com/api-reference/pacts/void-pact.md): Withdraw a pact that is out for signature. Its links stop working and the current signer is told. This cannot be undone.
- [Delete a draft](https://docs.signwithsigil.com/api-reference/pacts/delete-pact.md): Delete a pact that was never sent. A sent pact is voided instead, so its record stays.
- [Download the document](https://docs.signwithsigil.com/api-reference/pacts/download-document.md): The PDF exactly as it was sent, before anyone signed. Its SHA-256 is the pact's `sent_sha256`.
- [Download the signed PDF](https://docs.signwithsigil.com/api-reference/pacts/download-signed.md): The signed document with every signature, initial and value stamped on it. Its SHA-256 is the pact's `signed_sha256`.
- [Download the sigil](https://docs.signwithsigil.com/api-reference/pacts/download-sigil.md): The pact's sigil, its certificate of completion: each signer, when they viewed and signed (UTC), from which IP address, the consent they gave, both document hashes and the full event log.
- [List domains](https://docs.signwithsigil.com/api-reference/domains/list-domains.md): Your custom signing domains and their verification status.
- [The pact object](https://docs.signwithsigil.com/api-reference/objects/pact.md): A pact is a document sent to people for signature: a frozen copy of the PDF, its recipients in signing order, their fields, and an audit trail.
- [The template object](https://docs.signwithsigil.com/api-reference/objects/template.md): A template is a document with glyphs that you upload once and send many times. Its fields come from the glyphs in the document.
- [The account object](https://docs.signwithsigil.com/api-reference/objects/account.md): The account an API key belongs to: its plan, the documents it can still send, and its verified custom domains.

## MCP

- [MCP server](https://docs.signwithsigil.com/mcp.md): A hosted Model Context Protocol server, so AI assistants can list templates, send pacts and check who has signed. Nothing to install.
- [Connect a client](https://docs.signwithsigil.com/mcp/connect.md): Add the Sigil MCP server to Claude Code, Claude Desktop, Cursor, VS Code or any other MCP client with one URL and your API key.
- [Tools](https://docs.signwithsigil.com/mcp/tools.md): The ten MCP tools at a glance, with what each one does, whether it changes anything, and its REST equivalent.
- [get_account](https://docs.signwithsigil.com/mcp/tools/get-account.md): Who the assistant is acting for, how many documents are left, and which custom domains it can send under.
- [list_templates](https://docs.signwithsigil.com/mcp/tools/list-templates.md): The saved templates, most recently updated first.
- [get_template](https://docs.signwithsigil.com/mcp/tools/get-template.md): One template with its fields, so the assistant knows how many signers it needs and what each fills in.
- [list_pacts](https://docs.signwithsigil.com/mcp/tools/list-pacts.md): Pacts by status, most recently updated first. Defaults to `active` (drafts and sent), where the REST call defaults to `all`.
- [get_pact](https://docs.signwithsigil.com/mcp/tools/get-pact.md): One pact in full, optionally with the waiting signer's private link.
- [get_signing_status](https://docs.signwithsigil.com/mcp/tools/get-signing-status.md): A compact answer to "who has signed, and who is next?", cheaper for the model to read than the full pact.
- [create_pact](https://docs.signwithsigil.com/mcp/tools/create-pact.md): Create a pact from a saved template and, if asked, send it straight away. Uploading a one-off file is REST only.
- [send_pact](https://docs.signwithsigil.com/mcp/tools/send-pact.md): Send a draft: the first signer is emailed, and documents are charged.
- [resend_pact](https://docs.signwithsigil.com/mcp/tools/resend-pact.md): Email the current signer a fresh link. Free; the old link stops working.
- [void_pact](https://docs.signwithsigil.com/mcp/tools/void-pact.md): Withdraw a pact that is out for signature. It is marked destructive, so most clients ask you before running it.