The file you checked is the file they sign.
Holosign sends a document for electronic signature from the Holofin workflow that extracted and checked it, or from one API call. Signers open their own link and confirm a code sent to their email. You get a sealed PDF and an evidence log that records every step.
- No account for signers
- Real-time status
- Timestamped evidence file
Residential lease agreement
No. 2026-1042
Article 9. Signatures
The parties sign this agreement electronically. Each party receives the sealed copy by email, together with its evidence file.
The agreement takes effect on the date of the last signature.
The landlord
Paul Garnier
2026-11-15
The tenant
Camille Martin
2026-11-16
- Code verified
- 4 of 4 pages read
- Signed
Checked in one tool.
Signed in another.
A credit file, a lease, a supplier onboarding. The documents are collected and checked in one place, then the contract leaves for a separate signature tool: downloaded, uploaded again, the signers' names and emails typed a second time, the status copied back by hand. Two vendors, two evidence trails that never meet.
Nothing to upload twice
The workflow that extracted and checked the document sends it. The signers' names and emails can come from the extracted data.
No second vendor to review
Your documents and your clients' emails stay with the processor you already approved, under the same contract, hosted in the EU.
The outcome drives the next step
Signed, declined, expired: the run that checked the document moves on by itself, and a webhook tells your system.
The signer's journey
A link, a code, a signature.
No account, no app.
Your client signs from the email on their phone or computer, in a few minutes.
From: Acme Leasing via Holofin
Please sign: Rental agreement 2026-1042
Review and signThe invitation
Each signer receives an email with a link that is theirs alone.
Code sent to c***@example.com
The code
A 6-digit code goes to the same address. Only the owner of that mailbox can go on.
I have read the general terms
Read and acknowledge
The signer reads every page and ticks the acknowledgements you asked for.
Sign
By typing their name or drawing with a finger or a mouse.
The sealed copy, to everyone
When the last signer has signed, Holofin seals the file and emails the sealed copy to every signer.
Nobody on your side ever receives a signer's link or code, so nobody can sign in a client's place.
Signature fields
Signature, initials, date.
Where the document says.
Write markers in your template: [Signature 1], [Initials 1], [Date 1]. Each signer's mark prints in place of their marker: the first signer on 1, the second on 2.
A document without markers gets a signature page at the end. Before sending, one API call shows where every mark will print and warns when one would run off the page.
Article 9: Signatures
The landlord
The tenant
Signer 1 drew, signer 2 typed. Each mark replaces its marker.
Everything to get to signed.
Nothing to chase by hand.
Automatic reminders
Signers who have not signed get a new link every few days, on the schedule you set.
Real-time status
See who opened, who signed, and whether each invitation was delivered.
A wrong address, fixed
Correct a signer's email without starting over: the old link stops working, a new one goes out.
Up to 20 signers
Each with their own link and code, signing in any order.
Copies for your team
The sealed copy also goes to the addresses you choose, such as your contracts mailbox.
A deadline you choose
A request stays open from 1 to 90 days. After that, its links stop working.
Your message, their language
Add a personal note to the invitation. Emails and signing pages in French or English.
Initials on every page
Ask for each signer's initials at the foot of every page, not only on the last one.
Timestamped evidence file
Every step, chained.
Every file, sealed.
If a signature is ever challenged, the question is how it was made. Holosign records the answer as it happens, in a log nobody can quietly edit, and seals the signed file so any change shows.
- 09:14:02request.created0000…→fe61…
- 09:14:03invitation.sentfe61…→f821…
- 09:31:40link.openedf821…→9c8a…
- 09:31:41otp.sent9c8a…→6db0…
- 09:31:58otp.verified6db0…→0ae1…
- 09:33:12document.viewed0ae1…→922c…
- 09:33:20acknowledgement.accepted922c…→bdd5…
- 09:33:30signature.appliedbdd5…→a5be…
- 09:33:34seal.applieda5be…→2f14…
- 09:33:35timestamp.applied2f14…→d5b3…
- 09:33:41copy.deliveredd5b3…→41d7…
Each entry carries the hash of the entry before it. Remove or edit one, and every entry after it stops matching. Download the log as JSON with the API, next to the sealed PDF.
The sealed PDF
Your document
Signature page
Evidence pages
- Holofin's seal proves the file has not changed since it was signed, and that it came from Holofin.
- Timestamps come from an independent authority, not from our clock.
- Validation data and an archive timestamp travel inside the file (PAdES B-LTA), so it can still be checked after the certificates expire.
Use cases
Sign your everyday agreements
online, in minutes.
Legal value
Valid across the EU, under eIDAS.
An electronic signature cannot be refused as evidence just because it is electronic. Each Holosign signature is a simple electronic signature, verified by a one-time code sent to the signer's email address, sealed by Holofin and backed by its timestamped evidence file.
A step in your workflow.
Or one API call.
Signature step outputs
- signed→ Approve the file
- declined→ Manual review
- expired→ Manual review
In a workflow
Add a signature step after extraction and checks. The signers can come from the extracted data, such as the applicant's name and email on a form. The workflow continues on its own when the request is signed, declined, expired or failed.
See workflows →curl https://app.holofin.ai/api/v1.1/signature-requests \
-H "X-API-Key: $HOLOFIN_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"title": "Rental agreement 2026-1042",
"document_b64": "JVBERi0xLjcK...",
"document_type": "ordinary_contract",
"country": "FR",
"signers": [{"name": "Camille Martin",
"email": "[email protected]"}]
}'Through the API
Create a request with the PDF and its signers, follow each signer's status, correct an address or send a new link, then download the sealed PDF and the evidence log. A webhook tells you when a request is completed, declined, expired or cancelled.
Read the API reference →Coming next
Prepare the document
without writing a marker.
Today Holosign is the API and the workflow step. Here is what we are building on top.
A field editor
Open the document in Holofin, drop signature, initials and date fields on the page, and give each one to a signer.
Preparation from your AI assistant
Through Holofin's MCP server, an assistant finds the signers in the file, places the fields and prepares the request. You review it and send.
Codes by SMS
The one-time code sent to the signer's phone, for files where the phone number is the one you trust.
Questions
Holosign, in short
Yes. Under eIDAS, an electronic signature cannot be refused as evidence just because it is electronic. If a signature is ever challenged, the sealed file and its timestamped evidence file show how it was made.
No. The signer opens the link in their email, enters the 6-digit code sent to the same address and signs in the browser, on a phone or a computer.
No. The link and the code go only to the signer's address. Nobody on the sender's side ever receives them.
Yes, up to 20, in any order. Each signer gets their own link and code, and the file is sealed once the last one has signed.
The sealed PDF, with its signature page and evidence pages, and the evidence file as JSON. Every signer also receives the sealed copy by email.
Holosign is in early access, and its API is documented today so your team can build against it. Leave your work email and we will open your access.
Sign where you already check.
Holosign is in early access. Leave your work email and we will open your access.