Starting April 17, 2025 you can no longer create new V1 webhooks.
Note that existing webhooks v1 will continue to run in parallel to v2 after April 1, 2025, but users will be able to create only new webhooks v2. We will provide advance notice before any future deprecation of v1 webhooks functionality, ensuring a smooth transition.
Migrating to webhooks v2
The Bob Webhooks v2 adds reliability and stability by reducing the data sent on the payload, ensuring the events will be sent in the right order, and better retries handling when a webhook fails to send the event.
If you are using V1, please refer to Migrating to webhooks v2.
Check out Getting started with Webhooks before diving into this guide.
| Event | Type | Description |
|---|---|---|
| eSign Document Signing Complete | documents.eSign.completed | At the end of signing process the message will be sent. If the request has two signers and only one has signed, the message won’t be sent until the second signer completes signing. |
eSign Document Signing Complete Payload
{
"companyId": 468462,
"type": "documents.eSign.completed",
"documentId": 3208966,
"employeeId": "2683470122701554208",
"downloadUrl": "468462/documents/1644324879848_a63048e4-08a9-4e5b-bf17-3c8d399e2d89_16802375",
"signedBy": "2683470082411069966",
"creationDate": "2022-02-08T12:54:39.99"
}