Skip to content
Use cases

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.

Every flow is built the same way
  1. 01
    Generate the promptEsign Comply
    Pick the use case, your regions, your signers and your stack. You get one prompt with the exact rules for the signing screen.
  2. 02
    Your AI tool builds the pageYou
    Paste the prompt into Cursor, Claude Code, v0, Lovable, Bolt or Replit. The screen is yours: your layout, your words, your domain.
  3. 03
    The SDK reports the ceremonyEsign Comply
    The headless browser SDK attaches to your own elements and reports each step from the signer's browser straight to Esign Comply.
  4. 04
    Your server confirms the recordYou
    The API seals the record and returns a signed receipt. Your server confirms it with a secret key before anything is marked signed.

What stays the same in every flow

The document and the screen change from page to page. Three things do not.

POST /v1/sessions

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.

GET /v1/records/{id}

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.

Sealed at signing

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.

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 types

Are 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 generator

Do 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 DocuSign

Pick 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.

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