Skip to main content

Subscribe to outbound webhook events

Outbound webhooks let your systems react to activity in near real time. Instead of polling for changes, you register an HTTPS endpoint that the platform calls with a small JSON payload each time a subscribed event occurs — for example, when a Broadcast is delivered, opened, clicked, bounces, or a subscriber unsubscribes. This is the fastest way to keep a CRM, data warehouse, or automation in sync.

Before you begin​

  • Admin or developer access to the webhooks or integrations area of your account (confirm the exact steps in your account).
  • A publicly reachable HTTPS endpoint that returns a 2xx status quickly (do heavy work asynchronously).
  • The API/signing key used to verify that requests genuinely come from the platform.
  • A shortlist of the event types you actually need — subscribe narrowly to reduce noise.

Steps​

  1. Stand up an endpoint that accepts POST requests with a JSON body and responds 2xx within a few seconds.
  2. In your account, open the webhooks area and add a new subscription pointing to your endpoint URL.
  3. Select the event types you want to receive (delivery, open, click, bounce, unsubscribe, and similar).
  4. Save the subscription and copy the signing secret shown for it.
  5. In your handler, verify the signature on each request before trusting the payload, then acknowledge with 2xx.
  6. Send a test event (or trigger a small Broadcast) and confirm your endpoint receives it.

Result​

Your endpoint receives a webhook shortly after each subscribed event. Verified, acknowledged deliveries stop retrying; failed or slow endpoints are retried with backoff, so make your handler idempotent to tolerate duplicates.

Canonical terms: Author, Edition, Folder (Project Folder), Broadcast. See the Glossary.