Signatures that don't get in the way
Siggy sends documents for signature, keeps a sealed audit trail, and gives your engineers a real API instead of a portal to click through. Signers get one page and one task.
Three steps, no training required
Drop in a PDF and place fields right on the page — signature, initials, date, text, checkbox, name and email stamps. Each signer role keeps its own colour, so a three-party contract stays readable.
Document order, reminder cadence and signing roles — saved as a reusable definition. Send the same agreement a hundred times without rebuilding it.
One link, no account, works on a phone. When the last signature lands, Siggy seals the document and appends the certificate to the PDF itself.
Everything the day actually needs
Document order, reminder cadence and signing roles, saved once and reused — and every edit recorded with a before-and-after snapshot.
Place signature, initial, date, text, checkbox and stamp fields right on the page — colour-coded per signer role, or bound to a {{token}} in the document text.
Nudges on your schedule, stopping the moment a signer completes. No chasing by hand.
Every event HMAC-signed, https-only, and retried three times with backoff before it's given up on.
Document hash, signer email, IP and timestamps, hash-chained and attached to the finished PDF.
A contact book the whole workspace shares, an admin-and-signer split on everything that bills or configures, and per-tenant isolation from the first document onward.
An API first, a dashboard second
Launch a workflow in one call — PDFs in, signer links out. Status changes arrive as signed webhooks, keys are tenant-scoped, and every retry is idempotent.
curl -X POST https://signwithsiggy.com/api/v1/workflows \
-H "X-Api-Key: $SIGGY_API_KEY" \
-H "Idempotency-Key: order-4821" \
-F 'metadata={
"subject": "Master service agreement",
"message": "Please review and sign.",
"signers": [{
"firstName": "Dana", "lastName": "Reed",
"email": "dana@northwind.co", "role": "Customer",
"order": 1, "sendEmail": true, "returnSignLink": true
}],
"documents": [{
"fileName": "msa.pdf",
"anchors": [
{ "role": "Customer", "fieldType": "FullSignature", "tokenKey": "{{customer_sig}}" }
]
}]
};type=application/json' \
-F "msa.pdf=@./msa.pdf"Built to survive a dispute
An electronic signature is only worth what you can prove about it. Every Siggy workflow carries the evidence with it.
The signer confirms an attestation before the signature is taken. The confirmation, its timestamp and their IP are part of the trail.
Every event is SHA-256 chained to the one before it. Edit a row and the chain stops replaying — which is the point.
Each signature is sealed with an HMAC key held in Azure Key Vault for your workspace alone. Versioned, and rotated on schedule.
The certificate carries a verify link. Anyone holding it can recompute the seals and replay the chain — no account, no support ticket.
Twenty-four hours, single use, hashed at rest. Add a per-signer access code when the link alone isn't enough.
Choose 7, 30, 90 or 365 days at launch. Past it the workflow expires and the links stop working.
Priced by plan, metered by usage
Seats plus metered usage.
Plan details are unavailable right now.
Siggy's job is to produce the evidence. The signer confirms an attestation before signing, and the finished PDF carries a certificate of completion: the document's SHA-256, each signer's email, IP and UTC timestamp, the seal on each signature, and the full event trail — every event hash-chained to the one before it. Whether a particular agreement is enforceable where you operate is a question for your counsel, and we would rather hand them a record than a compliance badge.
No. One link, one page, signable on a phone — no download, no sign-up. The link is single-use and expires in 24 hours, and you can require a per-signer access code before the document opens. Every issue, open and view lands in the audit trail.
Upload the PDFs and place the fields once; a workflow definition is reusable from then on. If your documents are generated at runtime, drop a {{token}} where each signature belongs and Siggy binds to it — no placement step at all. For a large library we will do the first pass with you.
Three things: the API launches exactly what the dashboard launches, the signer gets one page instead of a guided tour, and the audit trail ships inside the document — hash-chained, and verifiable by anyone holding the link rather than by anyone willing to file a support request.
New launches stop; finished documents do not vanish. Closing a workspace opens a 30-day grace period — export what you need in that window, and tell us if the library is large enough that you would rather we helped.
Microsoft Azure, in the United States. There is no EU region yet — if that is a hard requirement, say so before you build, not after.
Send your first workflow today
Free for 50 workflows a month, no card, no sales call. Bring one contract and see how far you get in ten minutes.