Skip to content

Esign Comply documentation

Build the signing screen in your own interface. Esign Comply records the ceremony, checks selected conditions on its own record, and seals evidence you can verify without us.

Esign Comply is a signature compliance API. You build the signing screen; for direct browser ceremonies, we record events we receive and check selected conditions on our own record. Your team still owns legal duties such as sending renewal reminders, honoring cancellations, and delivering required copies. The prompt separates "Your obligations" from "Recommendations." We do not perform or verify your duties.

Send free text, JSON, and files through POST /v1/supplements. We seal each supplement with our receipt time and label it customer-supplied and unverified. Updates to state and country rules are delivered as guidance; new blocking conditions do not affect existing profiles until adopted. Read notices in the dashboard, email, webhook, API, or public changelog feed. Adding or removing a state does not require a code change to keep recording, but your flow may still need changes to meet new obligations.

Start with the quickstart to record your first test signature on localhost, or generate a prompt and let your AI coding tool do it.

Start here

Page What it gives you
Quickstart A test key, a first sealed test record with curl or the SDK, a registered domain, and the steps to go live
Generate a prompt A prompt for your AI coding tool, assembled from reviewed blocks for your use case, stack and rule packs
Browser SDK The headless SDK that observes the elements you built and reports the ceremony
API reference Conventions, every endpoint, every error code
Webhooks Event types, signature verification, retries
Verify a record The verification page, the API, and the offline verifier
Compliance: United States How the product is designed for U.S. federal and state rules
Compliance: Europe How the product is designed for the EU, the United Kingdom and Switzerland

For AI tools

Every documentation page has a Markdown version at the same path plus .md, for example /docs/quickstart.md. The index is at /llms.txt.

File Use
/llms.txt The index of every page, with rules for agents
/llms-full.txt Every documentation page in one file
/setup.md The runbook an AI coding tool follows with a test key
/auth.md How to handle keys: server only, never in chat, never committed
/pricing.md Plans, what counts as a signature event, certificate charges
/openapi.json OpenAPI 3.1 description of the /v1 API

You create the account and accept the terms once. No card. After that your AI agent can do the rest: create keys, register documents, build the flow, verify the domain and go live.

How it fits together

  1. Your server registers each document version, so the text is fixed and hashed before anyone signs.
  2. Your server creates a session for one signer and a bundle of document versions, and passes the session's client token to the browser.
  3. The browser SDK observes the screen you built and sends each step straight to Esign Comply: the documents presented, the notice, the signer's own action.
  4. Esign Comply writes the record, signs a receipt, and later attaches an external timestamp and a place in a public checkpoint.
  5. Your server confirms the record with its secret key before it grants access.

Each field in a record is labelled observed (seen by Esign Comply directly) or asserted (supplied by you). Verification checks integrity and the timestamp. It does not establish who acted or when the act actually occurred.

Guides

Guide Covers
Next.js with Supabase The full application: server module, migration, document pages, signup, confirmation, webhook, gate, NDA
Server confirmation Never trust the browser response: what to check and where
Test mode Test keys, test origins, reserved test signers, what is watermarked
Register a domain The one-domain rule, DNS and file verification, statuses, lapse
Consumer e-consent The ESIGN consumer consent steps: disclosure, access demonstration, consent
L2 verification A one-time code by email or SMS inside the ceremony
L3 passkeys A passkey challenge bound to the transaction
Re-acceptance Material changes, outstanding signers, the blocking screen
Supplements Customer-supplied text, JSON and files, sealed on receipt
Certificates The on-request Contemporaneous Record Statement: quote, confirm, share
Jurisdiction packs Selecting packs, modes, signer.region, facts, the dry run
Guidance and adoption Notices, update prompts, advise until adopted, adopt and roll back
AI app builders v0, Lovable, Bolt and Replit: where the secret key goes

Concepts

Concept Covers
The ceremony Sessions, steps, assurance levels, signature methods, failure modes
Observed and asserted What Esign Comply saw, what you told it, and what you sent later
Evidence The sealing pipeline, the receipt, the evidence report, the evidence package
Verification Checking a record with and without Esign Comply
Compatibility contract What can change, what cannot, and what you have to do in each case

SDKs and tools

Package Use
@esigncomply/browser Browser SDK: attaches to your elements and reports ceremony events
@esigncomply/react Hooks over the browser SDK. No visual components.
esigncomply Node server SDK: every method returns { data, error }
esigncomply CLI demo, check, documents publish, webhooks listen, verify
esigncomply-verify Offline verification of evidence packages

API reference

Area Endpoints
Conventions Base URLs, keys, idempotency, rate limits, pagination, versioning, the error envelope
Errors Every code, with status, type and what to do
Webhooks Events, signatures, retries
Documents Documents and immutable versions
Profiles Ceremony profiles
Jurisdictions The pack catalogue and the dry run
Sessions Sessions, events, verifications, completion
Records Records, evidence report, evidence package, receipt, annotations
Signers Records and status per signer, consent withdrawal, erasure
Certificates Quotes, issue, share links
Supplements and files Customer-supplied material
Guidance and adoption Notices, releases, update prompts, adopt and roll back
Verification and public log /verify, checkpoints, proofs, public keys
Account Domains, API keys, webhook endpoints, usage, conformance runs, prompts
Agent account API For AI agents with an agent token: account state, API keys, the domain, going live on the Free plan

Conformance and rule packs

  • Conformance rules: the 28 automated checks, what each measures, and how to fix a finding. Findings describe measurable design facts. They are not a statement that a flow is lawful or enforceable.
  • Jurisdiction packs: the catalogue of rule packs with every rule, fixed string, exclusion and fact key. A pack records which rules Esign Comply applied. It is not a statement that a flow meets the law of a jurisdiction.

Esign Comply is a record-keeping and compliance tooling service. It is not a law firm and does not provide legal advice. Whether an agreement is enforceable depends on your documents, your implementation, and applicable law.

Working with an AI tool? This page is also available as Markdown: /docs.md