Upload a PDF or Word file, or use a document generated from your template. Place the fields, choose who signs, and track each signature as it comes in. Everyone gets a sealed PDF with a certificate of completion.
Upload a PDF or Word file, or generate one from your template.
Add the signers and place their fields: signature, initials, date, name, text or checkbox.
See when each person is emailed, opens the document and signs.
Everyone receives a sealed PDF with a certificate of completion.
Upload a PDF or Word file, or fill one of your document templates and send what it generates.
Up to 20 people, each with their own fields.
Everyone at once, or one after another in the order you set.
Signature, initials, date signed, name, text and checkbox.
Save a document with its fields, and reuse it with new names and emails.
Signers sign from their email, with no app and no account.
See who has been emailed, who has opened the document, and who has signed.
Anyone who has not signed gets a reminder every 3 days, up to 3 times.
Simple electronic signatures under the ESIGN Act, UETA and eIDAS.
The signed PDF carries a digital seal, so a PDF reader shows it if the file is changed after signing.
Who signed, when, and from which IP address and device.
Every email, view, signature, reminder and correction, with the time.
Each signer agrees to sign electronically before signing, and the time is recorded.
A SHA-256 fingerprint of the document as it was sent, which identifies that exact file.
You can send documents for signature from a workflow or a form, and act on each signed document automatically.
Send a document a workflow generated for signature, wait for it, and carry on when it is signed, declined or expires.
Start a workflow when a document is signed, with the signed PDF ready for the next step.
Turn on Collect a signature on a form's image question. The signature goes into the document generated from each response.
Get a signed webhook on your own endpoint when everyone has signed.
Send documents for signature from Claude, Cursor or any MCP client, or from your own software through the REST API. Check who has signed, and get a webhook when everyone has.
curl -X POST https://automette.com/api/v1/sign_requests \
-H "Authorization: Bearer dg_your_api_key" \
-d '{
"signing_template_id": "a8f509d586dc4979ab64c0123",
"signers": [{ "name": "Ana Silva", "email": "ana@example.com" }]
}'Automette signatures are simple electronic signatures. In the United States they are covered by the ESIGN Act and UETA, and in the European Union they are simple electronic signatures under eIDAS. A few documents, such as wills and some court documents, cannot be signed this way in many places. If you are unsure about a particular document, ask a lawyer where you are.
Each request that everyone signs uses 0.10 credits, whatever the number of signers. Drafts, and requests that are declined, cancelled or expire, use nothing. Signing uses the same credit balance as everything else in Automette.
No. They sign from the link in their email. Only the person sending needs an account.
The document with every signature and value drawn on it, and a certificate of completion: who signed, their email address, when they opened, agreed and signed, their IP address, and the document's fingerprint. The PDF carries a digital seal, so a PDF reader shows it as changed if anyone edits it after signing.
Yes. Untick the setting before sending, and the signed PDF keeps the same pages as the original. The certificate is always available to download on its own.
Edit the signer on the request's page. The new address gets a fresh link, and the old one stops working.
Upload a PDF or Word file, place the fields, and send. Free to start.