How webhooks work

Snapdocs Connect supports bi-directional integrations by delivering events for status or call-to-action concerns. There are a few patterns for how these are configured across our various product APIs, with minor differences on what to expect spelled out below.

Subscriptions API - choose what to listen for

eClose and Quality Control share a single Snapdocs Connect subscription endpoint, but enforce event specific scopes. You create a subscription once with your callback URL and a list of events that we will Post to to that endpoint. Your key must be scoped for events by product type, such that eClose subscription scope is required for closing events and QC subscription scope is required for subscribing to QC events. Learn more in this section's API Reference tab.

Scope view	Example events	Full event list
Subscriptions: eClose scopes	closing status changes, document events, eSign events, notary events	eClose Events Catalog
Subscriptions: Quality Control scopes	package status changes, QC review results	Quality Control Events Catalog

Setup, payload handling, and the security model are covered by the shared pages in this section (Subscriptions API, Webhook security); each product's catalog above documents its events and payloads.

Other webhook systems

Product	How it differs
eVault	One webhook URL, registered by your Snapdocs Implementation Specialist, receives every event for your application's scopes — there is no per-event subscription. Configuration and payload layout: eVault Webhooks; event list: eVault Events Catalog.
Notary Connect	Status webhooks configured per integration alongside its X-AUTH-TOKEN key. The webhook reference has not migrated into this portal yet; it lives at notaryconnect.readme.io.