Skip to content
App builder · Replit

Add e-signatures to your Replit app

Your app lives on Replit and it needs signatures: terms at signup, a consent form, a contract. One prompt has Replit build the flow in your own pages while Esign Comply supplies the rules and keeps the independent record.

Free plan: 10 live signatures a month and a full test mode. No card required.

One prompt, from paste to record
  1. 01
    Add a test key to the project's secretsYou
  2. 02
    Paste one prompt into ReplitYou
  3. 03
    Replit builds the page and the server codeYou
  4. 04
    Acceptance reported from the user's browserEsign Comply
  5. 05
    Sealed record, receipt and timestampEsign Comply
  6. 06
    Server confirms, then creates the accountYou
Copy-paste prompt

The prompt to paste into Replit

Open your app on Replit and paste this into the chat. It builds a signup clickwrap: your Terms of Service and Privacy Notice, accepted with your own checkbox and your own button.

What the prompt tells Replit
  • Read setup.md, auth.md and llms.txt before writing anything.
  • Create the session on your server with the secret key, and send only the client token to the browser.
  • Attach the browser SDK to your own checkbox and button. No widget, no iframe.
  • Confirm the record on your server before the account exists.
  • Never invent an API method, and stop and ask when something conflicts.
Generate the prompt for your regions
Prompt for Replit
Add e-signature acceptance to this app's signup with Esign Comply. A new user ticks our own unchecked checkbox and clicks our own Create account button to accept the Terms of Service and the Privacy Notice. Esign Comply keeps the independent record.

Read these first and follow them exactly:
- https://esigncomply.com/setup.md
- https://esigncomply.com/auth.md
- https://esigncomply.com/llms.txt

Build
1. A server route that creates the session with the secret key from ESIGNCOMPLY_API_KEY and returns only the client token and the document version IDs to the browser.
2. The signup page: attach @esigncomply/browser with the client token to the page's own checkbox and button, and call complete() from the user's real click.
3. A server route that confirms the record with the secret key before the account is created, and refuses a made-up record ID.

Rules
- Ask me to add ESIGNCOMPLY_API_KEY in the Secrets pane, never in a file. Do not ask for the key in chat.
- Never invent API methods, packages or legal wording. If the docs do not cover it, or it conflicts with existing code, stop and ask me.
- Never pre-check the box or submit for the user.
- If a call returns domain_mismatch, tell me the origin in the error so I can add it to my test origins.

Run commands in the Shell and show their output, ending with npx esigncomply check --url on the running app. Write these rules to replit.md.
5 steps

How to run it in Replit

Replit is an online platform for building and hosting apps. This is the whole run, from a new Esign Comply account to your first test record.

  1. 01
    Create a free account and a test keySign up, then choose Create test key in the dashboard. The key starts with esc_test_ and is shown once. The Free plan needs no card, and test mode needs no registered domain.
  2. 02
    Add the key in the Secrets paneName it ESIGNCOMPLY_API_KEY. Your server reads it as an environment variable. Never put it in a file, and never paste it into the chat.
  3. 03
    Paste the promptReplit writes the server route that creates the session, attaches the SDK to your signup page and adds the route that confirms the record. It runs commands in the Shell and writes the rules to replit.md.
  4. 04
    Add your app's host to your test originsTest keys work on localhost with no setup. A hosted preview runs on its own host, so list that host under Domains, Test origins in the Esign Comply dashboard. If a call returns domain_mismatch, the message names the origin to add.
  5. 05
    Open the app and tick the boxTick the checkbox and click Create account. Your first test record is in the Esign Comply dashboard a moment later, with its conformance findings.
The 60-second result

What you have 60 seconds after Replit finishes

Open the running app and sign up once. This is what Replit wrote, and what Esign Comply holds a minute later.

  1. 01

    The server route that creates the session

    e.g. app/api/ceremony/route.ts

    It holds the secret key, pins the current version of each document and hands the browser a short-lived client token.

  2. 02

    Your signup form, with the SDK attached

    e.g. app/signup/signup-form.tsx

    Your markup and your styles. The SDK renders nothing: it watches your links, your checkbox and your button, and reports what the user did.

  3. 03

    The server confirmation

    e.g. app/api/signup/confirm/route.ts

    The record ID came from the browser, so the server reads the record with the secret key before the account exists.

// app/api/ceremony/route.ts
import { esc } from "@/lib/esigncomply";

export async function POST(request: Request) {
  const { signerId, email, attempt } = await request.json();

  const { data: session, error } = await esc.sessions.create(
    {
      profile: "prof_signup_4f1a",
      signer: {
        external_id: signerId,
        email,
        class: "consumer",
        country: "US",
      },
      documents: [
        { document: "doc_8Hq2", version: "current" }, // Terms of Service
        { document: "doc_Pv71", version: "current" }, // Privacy Notice
      ],
      context: {
        url: "http://localhost:3000/signup",
        locale: "en-US",
        purpose: "account_signup",
      },
    },
    { idempotencyKey: `signup-${signerId}-${attempt}` },
  );
  if (error) return Response.json({ error: error.code }, { status: 502 });

  // Save signerId and the pinned version IDs in server-owned state.
  return Response.json({
    clientToken: session.client_token,
    documents: session.documents,
  });
}

The example is written as Next.js route handlers. In Replit, the two server parts are server routes or backend functions that make the same two calls.

The record that appears

One sealed test record, kept by Esign Comply

Recordrec_Z4m8
simple · L1
RecordedWritten durably, receipt signed with ES256
TimestampedExternal RFC 3161 token over the record hash
AnchoredPublic anchor pending
Checkbox changed by a trusted user eventobserved
Terms of Service, version dv_3kT9observed
Server time 2026-11-21T15:03:20.291Zobserved
Signer email dana@example.orgasserted
record_hash sha256:5be7…example record

Your first test record opens in the dashboard with what was observed, what was asserted, and the conformance findings. It is sealed like a live record, on a separate test ledger, and its evidence report is watermarked TEST.

What Replit gets right with the rules, and wrong without them

A signup form that runs is easy to mistake for one that is finished. The prompt gives Replit the rules a running form does not show you, and the check measures each one.

CR-01block

Affirmative assent control

Without the rules

The checkbox ships already ticked, or a handler ticks it for the user to save a click.

With the prompt

The box renders unchecked and only a real user event changes it. The SDK records its state at load, and the check reports a pre-checked box or a scripted click at block level.

CR-02block

Notice text names every document

Without the rules

One generic line, "By signing up, you agree to our terms", with no document titles and no links.

With the prompt

The notice carries the registered title of every document in the session, each one linked, inside the same container as the checkbox and the button.

CR-04block

Notice and control in the same viewport

Without the rules

The agreement line sits in the footer or under a long form, below the fold on a phone.

With the prompt

The notice sits directly above the button in the same container. The SDK records both positions at the signing act, and the check runs your page at 390 by 844.

CR-07warn

Single primary action control

Without the rules

Email signup and two social sign-in buttons in one form, all styled as the main action under one notice.

With the prompt

One primary button inside the assent container. Social sign-in gets its own container, its own notice and its own session.

CR-08block

Document links resolve to the registered version

Without the rules

A link to /terms that serves whatever is in the repo today, or the legal text pasted into a component.

With the prompt

Every link serves the registered version by its ID, and the record pins that version by SHA-256 hash. Document text is never copied into your code.

Each row is a real conformance rule with its ID and its default level. Esign Comply runs 28 of them over your test records, and every finding names the rule, the measurement and the fix.

Go further with Replit

With the rules in replit.md, the next flow starts from them. Build the rest of the product on the same app.

A whole product

Build your own signing app

Upload a document, email each signer a link to your own application and collect the signatures there. There are 7 build guides, each with the steps and the code.

Build your own DocuSign
Your stack

Stack guides

The same integration written out for your framework and your host, with working code for the server, the browser and the confirmation.

Browse the stack guides
Live demos

Use cases

NDAs, contractor agreements, consent forms, order forms and terms updates. Each page has a live demo you can sign in test mode.

See the use cases
Prompt generator

The exact rules for your regions

Pick your use case, regions, signer types and stack. You get one prompt to paste into Replit, with your own document and profile IDs and the rule packs you selected.

Generate a prompt

Questions about Replit and e-signatures

Can I add e-signatures to an app built on Replit?

Yes. Paste the prompt on this page and Replit builds the flow in your own pages: a server route that creates the Esign Comply session, your signup page with the browser SDK attached, and a server route that confirms the record before the account is created.

Where do I put the API key on Replit?

In the Secrets pane, under the name ESIGNCOMPLY_API_KEY. Your server reads it as an environment variable. Never put it in a file, and never paste it into the chat. Start with a test key and add the live key to your production environment only.

Guide for AI app builders

Where does Replit keep the Esign Comply rules?

In replit.md. The prompt tells Replit to write the rules there, so later requests in the same app follow them without the prompt being pasted again.

Do test keys work on my Replit app's address?

Yes, once that host is on your list. Test keys work on localhost with no setup, and on hosts you add under Domains, Test origins in the Esign Comply dashboard. A call from an unlisted host returns domain_mismatch and names the origin to add.

How test mode works

How do I go live from a Replit address?

Register the host as your domain and verify it with a file: serve the token from the dashboard at /.well-known/esigncomply.txt. A host on a shared platform address verifies this way because you cannot add DNS records there. Then add your organization details and set the live key in production. The Free plan covers 10 live signatures a month with no checkout.

Register a domain

Build the flow on Replit. Leave the record to us.

Free plan: 10 live signatures a month and a full test mode. No card required.

Replit is a trademark of its owner. Esign Comply is not affiliated with it.

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