For the complete documentation index, see llms.txt. This page is also available as Markdown.

Webhooks

The Webhooks endpoints receive and process inbound callbacks from third-party e-signing providers — Adobe Sign and Dokobit/Signicat — as part of the e-contract workflow. These endpoints are called by the external provider, not by integrators directly.

Adobe Sign

Adobe Sign uses a two-step webhook pattern: first a verification GET request to confirm the endpoint, then POST requests for event notifications.

Adobe Webhook Verification

Adobe Webhook Verification

get

This GET method is used by Adobe eSign to verify the webhook configuration.

Header parameters
X-AdobeSign-ClientIdstringRequired

Unique Client ID sent by Adobe eSign for verification.

Responses
get
/webhook/callback/adobe

Adobe Webhook Event Listener

Adobe Webhook Event Listener

post

This POST method receives webhook event payloads from Adobe eSign.

Header parameters
X-AdobeSign-ClientIdstringRequired

Unique Client ID sent by Adobe eSign for verification.

Body
Other propertiesanyOptional
Responses
post
/webhook/callback/adobe

Dokobit

Dokobit Callback

Dokobit Callback

post
Responses
post
/webhook/callback/dokobit

No content

Signicat

Signicat Webhook

Signicat Webhook

get

This GET method is used by Signicat to notify about signed document events.

Query parameters
merchantAppIdstringRequired

Unique identifier for the merchant.

requestIdstringRequired

Unique identifier for the request.

Responses
get
/webhook/callback/signicat

No content

Was this helpful?