Build a signing flow for the document you have
Pick the document you need signed. Each page gives you the prompt for your AI coding tool, the steps the signing ceremony needs, and a live demo that runs a real ceremony against the real API.
Free plan: 10 live signatures a month and a full test mode. No card required.
- 01Generate the promptEsign ComplyPick the use case, your regions, your signers and your stack. You get one prompt with the exact rules for the signing screen.
- 02Your AI tool builds the pageYouPaste the prompt into Cursor, Claude Code, v0, Lovable, Bolt or Replit. The screen is yours: your layout, your words, your domain.
- 03The SDK reports the ceremonyEsign ComplyThe headless browser SDK attaches to your own elements and reports each step from the signer's browser straight to Esign Comply.
- 04Your server confirms the recordYouThe API seals the record and returns a signed receipt. Your server confirms it with a secret key before anything is marked signed.
Five documents, five signing flows
Every page follows the same order: try the demo, copy the prompt, read the steps, see what you build and what the record holds.
Build an NDA signing flow
Send a counterparty a link to your own app. They read the NDA, confirm an emailed code, type their name and sign. One sealed record per signer.
Prompt, steps and live demo Typed name · L2Build a contractor agreement signing flow
Make the agreement a step of your own onboarding. The contractor signs with a typed name and an emailed code, and work unlocks when your server confirms.
Prompt, steps and live demo Checkbox and button · L1Build a consent form with a recorded signature
A consent with its own checkbox, its own button and its own sealed record, kept apart from your terms of service.
Prompt, steps and live demo Typed name · L2Build an order form signing flow
Your quote builder, your totals, your page. The buyer signs the exact order they were shown, and the signature is recorded against it.
Prompt, steps and live demo Checkbox and button · L1Re-acceptance flow for a terms of service update
Publish the new version, find the signed-in users who have not accepted it, and block them on a screen with an unchecked box until they do.
Prompt, steps and live demoRecommended method and level, by document
This is Esign Comply's guidance for each document under the U.S. Federal rule pack. The method and the level are set on the profile, and you can change both.
| Document | Method | Level | Required steps | Document type |
|---|---|---|---|---|
| NDA | Typed name | L2, emailed code | 6 steps, with the emailed code | nda |
| Contractor agreement | Typed name | L2, emailed code | 6 steps, with the emailed code | contract |
| Consent form | Checkbox and button | L1 | 5 steps | consent |
| Order form | Typed name | L2, emailed code | 6 steps, with the emailed code | contract |
| Terms update | Checkbox and button | L1 | 5 steps | terms |
At L1 your app says who the signer is, from its own signed-in session, and Esign Comply records the act. L2 adds a one-time code that Esign Comply emails to the signer and confirms inside the ceremony. Each session returns its own required_steps, and your page reads the list from there. How the ceremony works.
What stays the same in every flow
The document and the screen change from page to page. Three things do not.
One signer per session
A session is one person signing one bundle of document versions. Two signers on the same document are two sessions and two sealed records, and your app tracks the packet and the signing order.
Your server confirms
The browser gets a receipt when the signer finishes. Your server still reads the record with its secret key, or handles the signed record.completed webhook, before it marks anything signed.
The record is kept outside your app
Each step reaches Esign Comply straight from the signer's browser. The record is hash-chained, signed with keys you do not hold, and timestamped by an outside RFC 3161 authority.
You build the page for the document. We keep the record of the signature.
Questions about signing flow use cases
Which documents can I build a signing flow for?
Any agreement you present in your own app: NDAs, contractor agreements, consent forms, order forms, terms of service and their updates, policies and custom agreements. You register the document through the API, your AI tool builds the signing screen, and Esign Comply records the ceremony and seals the record.
Document typesAre the demos on these pages real?
Yes. Each demo creates a real session against the real Esign Comply API in test mode, attaches the same browser SDK you install, and seals a real test record. Nothing is emailed, and no account is needed to run one.
Which signature method should I use for which document?
Esign Comply's guidance is a typed name with an emailed one-time code, level L2, for NDAs, contractor agreements and order forms, and an unchecked checkbox with a named button, level L1, for consent forms and terms updates. The prompt generator starts from those defaults and lets you change them.
Prompt generatorDo these flows work with several signers?
Yes. Create one session per signer on the same document version. Each signer gets their own ceremony and their own sealed record, and your app tracks the packet and the signing order.
Build your own DocuSignPick a document. Build the flow. Keep the receipt.
Free plan: 10 live signatures a month and a full test mode. No card required.
DocuSign and the other product names on this page are trademarks of their owners. Esign Comply is not affiliated with them.