Skip to main content
Webhooks let Scribe notify your own systems the moment something happens in your workspace: a conversion is recorded, a signature is published, a teammate joins or leaves, a campaign goes live. Instead of your tools asking Scribe for updates, Scribe pushes them — instantly. This is how teams sync signature-driven conversions into their CRM, alert IT when a signature fails to install in a mailbox, or mirror teammate changes into internal systems.
Webhooks are part of the Scribe API and require a plan with API access. Only workspace owners and admins can manage them.

​
Managing your webhooks

Open Settings → Webhooks (in the Technical section). The page lists every endpoint your workspace has configured, with the events each one subscribes to and its current status. Click Manage webhooks to open your workspace’s webhook portal, where you can:
  • Add endpoints — register any HTTPS URL your systems expose, or the URL of an automation tool.
  • Choose events — subscribe an endpoint to specific event types, or to everything.
  • Inspect deliveries — see every delivery attempt, its response, and replay failures.
  • Manage secrets — each endpoint has a signing secret so your systems can verify the notifications really come from Scribe.
Failed deliveries are retried automatically with increasing delays for about a day, so a short outage on your side loses nothing.

​
For developers

Building the receiving side? The webhooks developer documentation covers signature verification, delivery semantics, and the full event catalog with payload examples.