Resources
Everything you need to build on XDocs.
The API covers what the product does rather than a subset of it. Start with the reference, or hand the plain-text catalogue to an agent and let it read.
Build
API reference
Every endpoint under /api/v1, with its scope, parameters and response. Documents, envelopes, templates, data rooms, links, analytics, the audit trail and webhooks.
Read the referenceOpenAPI 3.1
The same catalogue as a machine-readable document, generated from the same list as the reference so the two cannot disagree.
Open the specFor AI agents
The whole API as plain text for a model to read, and an MCP server at /api/mcp that offers the assistant's own tools on your scoped API keys.
Open llms.txtWebhooks
Signed deliveries for the signing half and the sharing half alike — an envelope completed, a link opened, terms accepted, a copy downloaded — with a test delivery and a per-endpoint log.
See the events
Connect and run
Command line
A thin client over the public API with no dependencies beyond Node 20. It runs on a laptop, in a CI job or from a cron.
xdocs documents create --title "NDA" --markdown draft.md
Zapier
Every event is a trigger; creating a document, sending for signature and publishing a link are actions.
Incoming webhooks
URLs other software posts to: a draft from a form builder, a send when a deal closes, a link for every new lead.
Self-hosting
A Next.js app and Postgres, shipped with a Dockerfile and a compose file. It uses Clerk for sign-in, Vercel Blob for files and Resend for mail; with no billing keys set, nothing is limited.
docker compose up -d --build
Create a key and make the first call.
Keys are under Settings → Developer, scoped to what each one needs.