Help · Configuration
Webhooks and integrations
Signed HTTP calls to your own systems when a link publishes, a fan subscribes, or a release converts — with retries and a delivery log.
5 min · matches the current product
Webhooks (Label plan) push events into your own tools: a CRM that should learn about new fans, a Slack channel that should hear when a release converts, a data warehouse keeping its own copy. Every delivery is signed, retried with backoff, and logged with its response code — "did you actually call us" always has an answer.
Add an endpoint
Integrations → Webhooks → Add endpoint. HTTPS only. Pick the events you want, or none to receive all. The signing secret is shown exactly once at creation — store it; it cannot be recovered, only regenerated by recreating the endpoint.
Verify the signature
Each delivery carries X-DropRoute-Signature: sha256=<HMAC of the raw body with your secret>. Compute the same HMAC on your side and compare. Fan events carry ids only, never an email address — a webhook receiver is outside the privacy boundary.
Send a test ping and watch the log
The Send test ping button queues a signed ping delivery to that endpoint; the recent-deliveries log shows its status code within moments. Failed deliveries retry with exponential backoff; an endpoint that fails twenty times in a row is switched off with the reason shown, rather than hammered forever.
When it does not go to plan
- Deliveries show failed with no status code.
- The request never completed — DNS, TLS, or a timeout past ten seconds. The delivery row’s detail names which.