Document eSign completion webhook

wbhk

documentsESignCompleted

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.

Payload

companyId

int64

required

The company ID

type

string

enum

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.

Allowed:

triggeredBy

string

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.

triggeredAt

date-time

required

The timestamp when the event occurred

version

string

required

The webhook version

data

object

required

Event payload. Schema is defined by the webhook-integrations service (ESignCompletedEventData).

Headers

bob-signature

string

required

Base64-encoded signature sent with each webhook request. Use it to verify that the request came from Bob. To verify webhook authenticity, see How does Bob calculate the signature.

Responses

200

Webhook received successfully

Loading…

400Invalid webhook payload