Available events
Open and click tracking events require tracking to be enabled on your sending domain.
Event payloads
All sending events share a common envelope. Thetype field identifies the event, and the data field contains the event-specific payload along with the base email fields.
Base email fields (present on all sending events):
email.sent
Emitted when an email is accepted for delivery.email.delivered
Emitted when the email is successfully delivered to the recipient’s mail server.email.opened
Emitted when the recipient opens the email. Requires open tracking to be enabled on your sending domain.email.clicked
Emitted when the recipient clicks a link in the email. Requires click tracking to be enabled on your sending domain.email.bounced
Emitted when the email is rejected by the recipient’s mail server. Hard bounces indicate a permanent failure (for example, the address does not exist). Soft bounces are transient.email.complained
Emitted when the recipient marks the email as spam.email.rejected
Emitted when Nuntly refuses to send the email due to a policy or configuration issue (for example, the recipient is on a suppression list).email.deliveryDelayed
Emitted when delivery to the recipient is temporarily delayed. The email may still be delivered after retry attempts.email.failed
Emitted when the email could not be delivered after all retry attempts.Subscribe to sending events
Add sending events to your webhook configuration through the dashboard or the SDK.Handle sending events
Use the same signature verification flow described in handle webhook events. Here is a condensed example handling sending events:Learn more
Set up webhooks
Create and configure webhook endpoints
Handle webhook events
Implement signature verification and event handling
Receiving events
Webhook payloads for the receiving pipeline
Sending domains
Enable open and click tracking on your domain
