Skip to main content

Webhook event reference

Webhooks let your systems react to activity as it happens. When a subscriber opens or clicks a Broadcast, unsubscribes, or a delivery fails, the platform sends an HTTP POST to the endpoint you register. This page lists the outbound event types and the shape of the JSON payload each one carries.

Every event shares a common envelope (event id, event type, timestamp, and an object containing event-specific fields). The exact field names and which events are enabled are configured per account — (confirm the exact steps in your account).

Reference

Event typeWhen it firesKey payload fields
broadcast.deliveredThe message was accepted by the subscriber's mail serversubscriber_email, broadcast_id, edition_id, timestamp
broadcast.openedA subscriber opened the Editionsubscriber_email, broadcast_id, user_agent, timestamp
broadcast.clickedA subscriber clicked a tracked linksubscriber_email, broadcast_id, url, link_label, timestamp
broadcast.bouncedDelivery failedsubscriber_email, bounce_type (hard/soft), reason, timestamp
subscriber.unsubscribedA subscriber opted outsubscriber_email, list_id, source, timestamp
subscriber.complainedA subscriber marked the message as spamsubscriber_email, broadcast_id, timestamp

Field names above are representative; treat them as placeholders and verify against a live sample from your account.

Notes

  • Envelope. Each POST body wraps the event in a common structure — an id, an event (type), a created_at timestamp, and a data object holding the fields above.
  • Delivery and retries. Endpoints should return a 2xx promptly. Non-2xx responses are typically retried with backoff; design handlers to be idempotent using the event id.
  • Ordering. Events are not guaranteed to arrive in order. Use the timestamp, not arrival order, to reconstruct a sequence.
  • Security. Verify each request before trusting it (for example, a signature header or a shared secret) and respond only over HTTPS.
  • Batching. Some accounts receive one event per request; others may receive small batches. Handle both a single object and an array.

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