Skip to main content

Send outbound webhooks on Broadcast events

Push real-time notifications to your own systems when opens, clicks, and other Broadcast events occur. Instead of polling reports, a webhook sends an HTTP request to a URL you control the moment an event happens, so your CRM, data warehouse, or automation can react in near real time.

Before you begin​

  • Admin access to your account's integration or webhook settings (confirm the exact location in your account).
  • A publicly reachable HTTPS endpoint that can accept POST requests and return a 2xx response quickly.
  • A shortlist of the events you want to receive (for example: delivered, open, click, bounce, unsubscribe/complaint).
  • Optional but recommended: a shared secret or signing key so your endpoint can verify that requests genuinely came from the platform.

Steps​

  1. Open the integrations or webhooks area in your account settings.
  2. Create a new webhook (outbound endpoint) and paste your HTTPS endpoint URL.
  3. Select the Broadcast events you want to subscribe to. Subscribe only to what you will act on to keep traffic manageable.
  4. Add a signing secret or authentication header if your endpoint requires one, and record it securely on your side.
  5. Save, then use the test or "send sample" option to fire a sample payload and confirm your endpoint returns a 2xx status.
  6. Enable the webhook and send a real Broadcast to a small test audience to see live events flow through (confirm the exact labels and steps in your account).

Result​

Your endpoint receives an HTTP POST for each subscribed event, typically as a JSON payload identifying the subscriber, the Edition/Broadcast, the event type, and a timestamp. Failed deliveries are usually retried; check the webhook's delivery log to confirm successful (2xx) responses.

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