Send document events to your system with webhooks
A webhook posts a signed JSON message to your URL when a document is sent, opened, signed, completed, declined, expired or cancelled. Needs Pro; owners and admins set it up.
On this page
A webhook sends a message to a URL of yours each time something happens to a document, so your own system can act on it. Webhooks are part of Pro: they work in a workspace while one of its owners has Pro, and only owners and admins can manage them. Each workspace has its own.
Add a webhook
- Open Settings & branding in the account menu and go to Integrations.
- Press Add webhook.
- Enter the Endpoint URL. It must start with
https://and be public: addresses in private networks, Sealsimple's own addresses and URLs with a user name and password are refused. - Add a Name if you like, pick the Events (all are ticked to start with) and press Add webhook.
- Copy the Signing secret that appears, and press Send test event.
A workspace can have up to 10 webhooks.
Events
document.sent: Document sentdocument.viewed: Opened by a recipient, once per recipientdocument.signed: Signed by a signer, once per signerdocument.completed: Completed: everyone signeddocument.declined: Declineddocument.expired: Expireddocument.canceled: Cancelled
What we send
A POST with a JSON body: id (the same on every try, so you can skip duplicates), event, created_at, workspace_id, a document with id, title, status and url, and for events about one person a recipient with name, email and role. A cancelled document has the status voided. The signed PDF itself isn't sent: fetch it with the REST API once the document is completed. The test event has the event test and a made-up document and signer.
Check the signature
Every request has a Sealsimple-Signature header like t=1700000000,v1=…, next to Sealsimple-Event and Sealsimple-Delivery. To check it:
- Take the raw request body, exactly as it arrived.
- Read
t(a Unix time in seconds) andv1from the header. - Compute the HMAC-SHA256 of
t, a dot and the body, with your whole signing secret as the key, in lowercase hex. - Accept the request only if this equals
v1(compare in constant time) andtis at most a few minutes old.
Under How to connect, Check the signature (Node.js) shows this as code, with Copy code. New secret replaces the secret at once, so update your check straight after.
Retries, the log and pausing
Answer with a 2xx status within 10 seconds. Otherwise we try again later, up to 6 tries in all over about a day. Redirects aren't followed, and an answer of 410 stops the tries. The Delivery log shows the last 50 messages with your endpoint's answer, and Resend sends one again.
After 20 failed deliveries in a row, we pause the webhook (Paused after failures) and email the workspace's owners. Fix the endpoint, switch the webhook back on and resend what you need from the log. You can also pause a webhook with its switch: events that happen while it's paused aren't sent later. Without Pro, webhooks stay but send nothing.
Is there an API?
Yes, on Pro. Webhooks tell your system when something happens; the REST API lets it act: upload and send documents, and fetch their status, the signed PDF and the audit trail. Start with Use the API, or see every endpoint in the API documentation.