HIhibob
Docs Webhooks

Document eSign completion webhook

Webhook sent when a document e-signing process is completed. The event will be sent at the end of the signing process. If the request has two signers and only one has signed, the event will not be sent until the second signer completes signing.

In the right panel, open Examples and select Payload Example to see a real payload.

postWebhookdocumentsESignCompleted

Headers

bob-signaturestring required
Example:EQScIBkAtTKFW0ictgt5zzOsqIc2+xGEsM88jOdLuW4CM/a3gLEfrKV+IC5IHx0xbirzLKPIfaZjCGwzuiyI8w==

Base64-encoded signature sent with each webhook request. Use it to verify that the request came from Bob. To verify webhook authenticity, see <a href="https://apidocs.hibob.com/reference/getting-started-webhooks#how-does-bob-calculate-the-signature" target="_blank">How does Bob calculate the signature</a>.

Payload

companyIdinteger required

The company ID

type'documents.eSign.completed' required

This event is sent at the end of the document e-signing process. If the request has two signers and only one has signed, the event will not be sent until the second signer completes their signing.

triggeredBystring required

Indicates who/what triggered the event. When set to "system", it means the event was triggered by an automated background process. Could also be an employee ID if triggered directly by a user action.

triggeredAtstring date-time required

The timestamp when the event occurred

versionstring required

The webhook version

Response

Webhook received successfully

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.