Signed today, not next week
Place a field for each signer, send one link, and get back a sealed PDF with its certificate and audit trail inside. It opens on any phone, on a weak connection, with no account to create.
Signature
A. Diallo
Date
16 Aug 2026
What E-signature gives you
No courier, no trip across town
The document that needed a printer, a driver and half a day comes back signed before the meeting about it ends. Printing, driving and scanning stop being part of the contract.
Nothing for the signer to install
They get a link and open it in the browser already on their phone. No account, no app, no explaining call. The person on the other end has never used Sedeya and does not need to learn it.
The proof does not live on our servers
The certificate and the audit log are inside the finished PDF. Forward the file to a lawyer, a bank or a regulator and the evidence goes with it — nothing to look up, nothing that depends on us still being here.
How E-signature works
From your desk to their phone in three minutes
Drop in the PDF, drag a field onto each blank, add the signers, send. That is the whole of your side of it.
- Signature, initials, name, email, date, text, number, checkbox, radio and dropdown, dragged onto the page where the printed form already leaves a blank
- Signers one after another when the second signature depends on the first, all at once when it does not
- Reminders go out on the schedule you set, and documents expire instead of sitting open forever
- The contract you send fifty times becomes a template, and bulk send turns it plus a spreadsheet into fifty envelopes
A link, on the phone they already own
The signer opens the link in the browser already on their phone. No account, no app, no explaining call — which matters, because they never chose to be here.
- Works on a weak connection, on a phone that is not new
- Nothing to install, and nothing to create an account for
- A passkey, two-factor check or one-time code when a click is not enough
Sealed, the moment the last signature lands
You watch it move — sent, viewed, signed — and when the last person is done the finished PDF comes back flattened and sealed, with its certificate and audit log inside.
- Live status shows who is holding it up, so chasing is one message to one person
- The sealed file is the record: nothing to look up on our servers later
What ends up inside the finished file
Not a badge on a website. The evidence is written into the PDF itself, so it travels with the document wherever it goes.
A certificate page
Appended to the document: who signed, when, from which address, and the result of the identity check if you required one. It is a page inside the PDF, not a link to a page on our site.
A full audit log
Sent, opened, viewed, signed, completed — every action timestamped, for every recipient. The sequence is what answers “they signed before they ever saw the annex” a year later.
A cryptographic seal
The finished file is flattened and signed. Change one byte afterwards and the seal breaks, which is the point — and anyone can check it without asking us.
Every field as submitted
The name typed, the date picked, the box ticked, the option chosen, captured exactly as the signer left them, so the record and the document can never disagree.
API
Everything the interface does, the API does too
A REST API with a published OpenAPI specification and interactive documentation. Signed webhooks tell your system the moment a document is viewed, signed or completed.
- API tokens issued per team, never a personal login
- Signed webhooks your endpoint can verify
curl https://api-staging.sedeya.com/v1/envelopes \
-X POST \
-H "Authorization: Bearer $SEDEYA_API_TOKEN" \
-F 'payload={"title":"Consulting agreement","type":"DOCUMENT","teamId":1,"recipients":[{"email":"jane@example.com","name":"Jane Doe"}]}' \
-F "files=@contract.pdf"
Most documents do not need ceremony. They need to leave your desk, reach the other person, come back signed, and still be findable a year later. That is the whole job, and it still usually involves a printer, a driver and half a day nobody has.
The rest of it is a question of who you are depending on. A signed PDF from Sedeya carries its own certificate and its own audit log — the evidence outlives us, and nobody has to come back to our servers to read it. At the top tier, the whole thing runs on yours.
The rest of the product set
The other pieces of the platform, and what each one does.
Frequently asked questions
The certificate page and audit trail are inside the PDF itself — address, timestamp and every action taken, for every recipient. You forward the file and the evidence goes with it.
No. They sign through a link, in the browser they already have. If a click is not enough for a particular document, you can require a one-time code or a two-factor check before it opens, and a passkey at the moment of signing — still with no account to create.
Yes. Bulk send takes a template and a spreadsheet of recipients, and creates one envelope per row.
An offer letter, an NDA, a vendor agreement or an internal policy goes out to someone you already know, and the link is enough. A first contract, an onboarding file or a payment mandate goes to someone you do not, and “prove it was really them” has to hold up in front of a third party later. That is what E-verification adds: the signer establishes who they are before the document opens, and the result is recorded next to the signature in the same sealed PDF.
Bring E-signature to your team
Talk to us about rolling it out, or start today if it is already live.
Get started