Consent, captured properly
The signer accepts the E-Sign disclosure before anything else, and that acceptance is recorded with the document, the timestamp and the address it came from. ESIGN and UETA ready.
A lead usually crosses four systems between the landing page and the signed agreement, and loses something at every hand-off. LimeBase is one record that survives the whole trip. The signature end — Lime Docs — is available today, and it works perfectly well on its own.
Get the retainer signed while the claimant is still on the phone, and keep the proof. Every envelope returns a sealed PDF and a Certificate of Completion.
How it fits together →REST over HTTPS, JSON in and out. Create an envelope, attach a document, place typed fields, send. HMAC-signed webhooks tell you when it completes.
Quickstart →If a signature arriving two days late costs you the client, the delay is the problem worth solving. The stack was shaped in intake work, then generalized.
Upload a PDF, place the fields where they belong, and every signer gets a secure, single-use link. They sign on any device without creating an account, and you get back a sealed PDF and a tamper-evident Certificate of Completion. ESIGN and UETA ready.
The line runs capture, route, sign. Each product is sold and used on its own, and together they carry one identifier from the landing page to the signed agreement. Lime Cert is not a fourth stop — it sits underneath and certifies each transaction as it happens. Sign is available today; Cert follows in Fall 2026, Forms in Winter 2026 and Flows in Spring 2027.
Forms that adapt to live signals, adding a verification step when a session looks synthetic instead of taking the lead at face value.
Send the lead to the right owner the moment it qualifies, with its full history attached, rather than a lossy hand-off that drops half the context.
Send the retainer while the claimant is still on the phone. Sealed PDF, hash-chained audit trail and a Certificate of Completion on every envelope.
Every stage above produces a transaction worth being able to prove later. Lime Cert works natively against all three, recording what was shown and agreed at the moment it happened, so the evidence is contemporaneous rather than reconstructed from logs afterwards.
REST over HTTPS, JSON in and out, versioned and documented. The sandbox is free — swap the test key for a live one when you are ready.
curl -X POST https://api.limebase.app/v1/envelopes \ -H "Authorization: Bearer lsk_test_…" \ -H "Content-Type: application/json" \ -d '{ "title": "Retainer agreement", "signers": [ { "name": "Dana Reyes", "email": "d.reyes@example.com", "role": "signer", "signingOrder": 1 }, { "name": "Placeholder Law LLP", "email": "counsel@example.com", "role": "signer", "signingOrder": 2 } ] }' # 201 Created { "id": "env_4c81b2", "status": "draft" }
// 1. the envelope and who signs it const env = await api("POST", "/v1/envelopes", { title: "Retainer agreement", signers: [{ name: "Dana Reyes", email: "d.reyes@example.com" }], }); // 2. the document to be signed const doc = await upload(`/v1/envelopes/${env.id}/documents`, pdf); // 3. where the fields go, in page coordinates await api("POST", `/v1/envelopes/${env.id}/fields`, { fields: [ { type: "signature", signerId: env.signers[0].id, documentId: doc.id, page: 3, x: 72, y: 560, w: 220, h: 48 }, { type: "date_signed", signerId: env.signers[0].id, documentId: doc.id, page: 3, x: 320, y: 560, w: 120, h: 28 }, ], }); // 4. deliver it — each signer gets a single-use link await api("POST", `/v1/envelopes/${env.id}/send`);
// Every event carries a signature header you verify // against your endpoint secret before trusting it. app.post("/hooks/limebase", async (req, res) => { if (!verify(req.headers, req.rawBody, SECRET)) { return res.sendStatus(401); } switch (req.body.type) { case "envelope.sent": break; case "signer.signed": break; case "envelope.declined": break; case "envelope.voided": break; case "envelope.completed": await crm.attach(req.body.envelope.id); break; } res.sendStatus(200); });
The signer accepts the E-Sign disclosure before anything else, and that acceptance is recorded with the document, the timestamp and the address it came from. ESIGN and UETA ready.
Each event is hashed against the one before it. Change a page or a timestamp after the fact and the chain no longer verifies, which is the point of keeping one.
Social security, EIN and bank account numbers are encrypted individually and bound to the row that holds them, so a stray copy decrypts to nothing. Masked everywhere they are displayed.
limebase.app is the workspace. Every product you own appears in the same place, under one login and one bill.
Who was sent what, who opened it and who has stalled. Nudge a signer or resend from the same view, and the audit trail records both.
Build a document once with its fields and roles already placed, then send it against new matter data without rebuilding the layout each time.
Rotate keys per environment, replay a failed webhook, and read the last request and response body when an integration misbehaves.
Invite colleagues with roles, watch usage against your plan as it accrues, and download a monthly invoice — including on the free plan.
You pick a plan, it carries a monthly envelope allowance, and you are billed the same amount each month — no per-envelope meter to watch and no surprise overage. Start mid-month and the first invoice is prorated to the days you actually had. Lime Docs is priced on its own and always will be.
No. Lime Docs is a complete product on its own, priced on its own, and it will stay that way. Plenty of teams will only ever want the e-signature API. Taking the whole suite is for teams who want one record across the whole pipeline — it is a bundle, not a prerequisite.
Lime Docs, in full. The rest have dates: Lime Cert in Fall 2026, Lime Forms in Winter 2026 and Lime Flows in Spring 2027. Until each one ships you will see it in your workspace marked with its release window, and you are not billed for it — we would rather show you the date than take your money for a waitlist.
Lime Docs is built to the ESIGN Act and UETA: the signer is shown and accepts an electronic-records disclosure before signing, their intent is captured explicitly, and the resulting record is tamper-evident and reproducible. Every envelope produces a Certificate of Completion listing the events, timestamps and addresses. That is evidence about the signing — it is not legal advice about your particular document, and it does not cover the few document types that statute excludes.
Three field types are classified sensitive — social security number, EIN and bank account number. Each is encrypted individually, bound to the record that holds it, and never written alongside a plaintext copy. They are masked wherever they are displayed, including to you. A routing number is deliberately not on that list: it is printed on every cheque and published by the ABA, so masking it costs the sender legibility and hides nothing. An unrecognised field type is treated as sensitive rather than assumed safe.
That was a design constraint, not an afterthought. The signing page is server-rendered and works on old phones, slow connections and browsers several versions behind, including with scripting disabled. Signers never create an account — they follow a single-use link sent by email or SMS.
One flat charge a month for your plan, and an envelope allowance that resets each calendar month. Nothing is metered per envelope, so the number on the invoice is the number you expected. If you start partway through a month, the first invoice is prorated and says so on the line item — the arithmetic is printed rather than left for you to work out. The free plan is invoiced too, at zero: it runs the same billing pipeline every month, so by the time real money moves the only new part is taking payment.
We are not publishing a price list while the other products are still in flight — quoting a suite before three quarters of it ships is how you end up repricing in public. Lime Docs itself has a free tier you can start on today with no card, and we will quote you directly for anything beyond it. Talk to us for committed-volume and white-label terms.
The free plan needs no card. Three envelopes a month, the full API, and an invoice at zero so the billing is proven before you ever pay one.