A webhook tells your own system the moment something happens: a document sent, opened, signed, or finished. Endpoints live under Developers. Add one with the address that receives them, a label, and the events it should be sent.
For developers.
A webhook tells your own system the moment something happens: a document sent, opened, signed, or finished. Endpoints live under Developers. Add one with the address that receives them, a label, and the events it should be sent.
Its signing secret is shown once, here. Every delivery is signed with it, so your system can check that it came from SignSealer and was not changed on the way. The guide has the few lines that do the check.
Each endpoint keeps what was sent to it. Here is yesterday's finished waiver, delivered, and this morning's attempt, refused with an error from the booking system. Once the problem is fixed, send it again, and the new attempt is marked as a replay of the old one.
If a secret might have been seen, rotate it. The new one is shown once, and the old one keeps signing beside it for a day, so your receiver can switch over without dropping a delivery.
Build against a test key first. Endpoints registered with a test key receive the sandbox's events, signed the same way, and nothing real is sent to anybody. When your handler is ready, move to a live key for production: the endpoints here receive your real documents' events.