Event Webhooks
Configure and verify email Webhooks, including seven event types, signatures, idempotency, and manual failure troubleshooting.
Webhooks push email events to your server. Callback configuration is API Key-level and currently requires platform operators; the customer console has no self-service page for Webhook URLs, subscriptions, signing secrets, or delivery logs.
Before activation
- Provide a publicly accessible HTTPS callback URL with a valid certificate. URLs resolving to private, loopback, link-local, or other reserved addresses are rejected.
- Confirm the event types and callback authentication mode.
- Ensure the receiver returns 2xx within 10 seconds without relying on redirects, cookies, or automatic retries.
- Implement deduplication by
eventIdand reconciliation by Message ID.
Subscribable events
eventType | Meaning |
|---|---|
delivered | The receiving server accepted the message; inbox placement and reading are not guaranteed. |
bounced | A bounce event was received. |
complained | A spam complaint was received. |
opened | An open was recorded; tracking configuration and client privacy behavior affect this event. |
clicked | A link click was recorded. |
delivery_delayed | Delivery is delayed, not finally delivered. |
send_failed | The platform Sender produced a definite failure or rejection. |
Open and click events depend on channel tracking support and configuration. send_failed is message-level and has an empty recipient string.
Request format
Last updated on