E-Signature with Lovable
Add legally binding e-signatures to your Lovable app with ready-made prompts for embedded signing, the template builder and webhooks.
Let users sign inside your app
The fastest path to a signature. Your backend creates a submission, DocuSeal returns an embed_src for that one signer, and the form renders in place. No redirect, no email round-trip.
- The API key stays on the server, never in the browser
- The submitter carries the name and email, so fields arrive prefilled
- No signature request email, the signer never leaves your app
Prompt for Lovable
Add DocuSeal (https://www.docuseal.com) embedded signing so a user can sign a document without leaving my app. Build it the way the rest of this project is built. Read the reference before you write any code. It is plain Markdown and it is current: - https://www.docuseal.com/docs/api.md covers authentication, creating a submission and what comes back. - https://www.docuseal.com/docs/embedded/form/react.md covers the signing form component itself, with every attribute and callback. - https://www.docuseal.com/llms.txt indexes the rest of the site. Any page works as Markdown by adding .md to its URL. Two things the docs cannot answer, so ask me: - Which document gets signed, and where in the app signing starts from. - Where this project keeps server-side secrets. My DocuSeal API key goes there and must never reach the browser, so every call to the API happens on the server. When you are done, tell me anything you could not confirm from the docs.
Give your users a template builder
Drop DocuSeal's WYSIWYG builder into your app. Upload a PDF, place fields, save. Your users never see a second product.
- Authorization JWT signed on the server, so each user gets their own templates
- Opens an existing template or a fresh PDF
- onSave hands back the template id the signing flow needs
Prompt for Lovable
Add DocuSeal's embedded template builder (https://www.docuseal.com) so that users can prepare documents without leaving my app. Put it wherever this project already keeps its documents screens. Read the reference before you write any code: - https://www.docuseal.com/docs/embedded/builder/react.md covers the builder component and the token it takes, including every claim and backend examples for signing it. - https://www.docuseal.com/docs/api.md covers the REST API, including how templates are identified. - https://www.docuseal.com/llms.txt indexes the rest of the site. Any page works as Markdown by adding .md to its URL. Proactively ask me about implementation details, using the features and customization options documented in the reference, so the builder works the way my team needs it to. Ask me before you start: - Where this project keeps server-side secrets. The token is signed with my DocuSeal API key, so it can only be minted on the server. - Who is allowed to open the builder, and I will point you at the auth this project already has. When you are done, tell me anything you could not confirm from the docs.
Store every signed PDF automatically
submission.completed fires the moment the last party signs, carrying the finished PDFs and the audit log. This prompt covers verifying the signature and keeping your own copy before the links expire.
- HMAC-SHA256 signature check on a public endpoint
- DocuSeal retries failed deliveries for 48 hours
- Document links expire in 40 minutes, so copies get downloaded
Prompt for Lovable
Set up DocuSeal webhooks (https://www.docuseal.com) so my app finds out when a document is fully signed and keeps its own copy. Store it the way this project already stores things. Read the reference before you write any code: - https://www.docuseal.com/resources/use-webhooks.md covers registering a webhook and verifying the signature on every delivery, with working code. - https://www.docuseal.com/docs/api.md lists every event and its exact payload. Check which event fires when, they are not interchangeable and their payloads are shaped differently. - https://www.docuseal.com/guides/download-signed-documents.md covers retrieving the signed files and what not to do with the URLs. - https://www.docuseal.com/llms.txt indexes the rest of the site. Any page works as Markdown by adding .md to its URL. Ask me where this project keeps server-side secrets, the webhook signing secret goes there. When you are done, give me the deployed URL, tell me where in DocuSeal to register it and where the signing secret lives, and flag anything you could not confirm from the docs.
Get started in three steps
Create a free account
Sign up at docuseal.com, upload one PDF, place the fields, and note the template id you'll sign against.
Copy your API token
Open the API page in your console and copy the key. Lovable will ask for it and store it as a Supabase secret.
Paste a prompt
Drop the embedded signing prompt into Lovable's chat, hit send, and sign your first document in the preview.
The whole UI in one component
The React component implements the entire signing UI integration. Set src to a template link when anyone can sign, or to the per-signer link the API returns for a submission. The same component ships for Vue, Angular and plain JavaScript, and every signer gets a mobile-optimized form in 14 languages.
import React from "react"
import { DocusealForm } from '@docuseal/react'
export function App() {
return (
<div className="app">
<DocusealForm
src="https://docuseal.com/d/LEVGR9rhZYf86M"
email="signer@example.com"
onComplete={(data) => console.log(data)}
/>
</div>
);
}
Signatures your legal and ops team approve
Legally binding
Aligned with the ESIGN Act and UETA in the US and eIDAS in the EU. Every completed submission carries a time-stamped audit log PDF.
Priced per document
The API and embedded signing are billed per completed document on top of your plan. Signers never need an account or a seat of their own.
Secure and compliant
DocuSeal Cloud is SOC 2 and ISO 27001 certified, HIPAA and GDPR compliant, with EU data residency for customers on docuseal.eu.
Webhooks and API
A full REST API, with eleven webhook events across forms, submissions and templates to keep your app in sync.
Signs on any device
Typed, drawn or uploaded signatures, mobile-optimized, with signing available in 14 languages.
Your branding
Pass your own logo and custom CSS to the embedded form, so signing looks like the rest of your app.
Frequently Asked Questions
Do I need a paid plan?
Yes. Embedded signing, the embedded builder and webhooks are all Pro features, and documents signed through the API or the embed are $0.20 per completion on top of the plan. Full pricing.
Where does the API key live?
On your server, never in the browser. Each prompt says so and tells the agent to use whatever this project already keeps secrets in, which in a Lovable app is a Supabase secret read from an edge function.
Which template do the prompts sign?
Whichever template id you pass in. Upload one PDF in DocuSeal first, then hand Lovable that id, or run the template builder prompt and let your team create their own. Pass the role name your template uses.
What if the prompt drifts?
Paste it again with the file it should fix and ask the agent to re-read the reference page that prompt links. Most drift is an agent working from memory instead of the docs.
Ship e-signature today
Create your API key, paste the embedded signing prompt into Lovable, and the agent implements the integration from our documentation.