Event Types
List of supported event types and their payload.
sent
Occurs when the email is successfully sent to the recipients's mail server.
{
"type": "sent",
"createdAt": "2025-11-28T06:29:34+00:00",
"messageId": "fdf8fcd2-e9f7-48bb-99f4-34e9093280d5",
"data": {
"id": "be55a7aa-2326-421b-ac2f-997da114c2e2",
"customerReference": "testing-integration-mode"
}
}
delivered
Occurs when the email is successfully delivered to the recipients's mail server.
{
"type": "delivered",
"createdAt": "2025-11-28T06:29:46+00:00",
"messageId": "2a53f2c1-e505-4c0b-b0ae-b0e7fcf0ebf2",
"data": {
"id": "f10ae494-2ad0-4973-82ae-35d73e844230",
"customerReference": "testing-integration-mode"
}
}
opened
Occurs when the recipient opened the email.
{
"type": "opened",
"createdAt": "2025-11-28T06:30:47+00:00",
"messageId": "8f8c777c-9f85-4661-b891-0e87596380cc",
"data": {
"id": "99820716-dc42-4e88-8ca1-ed0c6c9889bc",
"customerReference": "testing-integration-mode"
}
}
Open tracking needs to be enabled within tracking settings to receive opened events.
clicked
Occurs when the recipient clicks on an email link.
{
"type": "clicked",
"createdAt": "2025-11-28T06:30:54+00:00",
"messageId": "40beeb23-e91d-473c-bcc9-743c6d6d026d",
"data": {
"id": "98cfb8ac-30ac-42cc-a6f9-dac018cd99a3",
"customerReference": "testing-integration-mode"
}
}
Click tracking needs to be enabled within tracking setting to receive clicked events.
bounced
Occurs when the recipient's mail server permanently rejected the email.
{
"type": "bounced",
"createdAt": "2025-11-28T06:29:57+00:00",
"messageId": "8814fd39-1ba7-4d94-bd4f-fbb2a85ea5ba",
"data": {
"id": "c7699f04-92b1-44b7-836a-8ce51cf2a2ad",
"customerReference": "testing-integration-mode",
"bounce": {
"type": "Bounce",
"subType": "Integration Mode",
"message": "Integration Mode: bounced webhook simulation."
}
}
}
type: Soft Bounce
All messages classified as Soft Bounce will be automatically retried by our system over a 24-hour period. Each retry attempt will trigger a new webhook notification, referencing the same message ID.
After max. 7 unsuccessful retry attempts, our system will stop retrying the message and mark it as dropped. You will receive a failed webhook notification indicating that the maximum retry attempts have been reached and the message has been dropped.
| subType | message |
|---|---|
| Transient Failure | Delivery delayed: A temporary failure occurred. Our system will continue to retry delivery for a limited time. |
| Quota Issues | Delivery failed: The recipient's mailbox is full and cannot accept new messages at this time. Please try resending your email later or contact the recipient to clear space. |
| No Answer From Host | Delivery delayed: The recipient's mail server is currently not responding. Our system will continue to retry delivery for a limited period. |
| Bad Connection | Delivery failed: There was a network connection problem with the recipient's mail server. This may be a temporary issue and will be retried automatically. |
| Dns Failure | Delivery failed: The recipient's mail server address could not be resolved due to DNS issues. Please verify the recipient's email address and try again. |
| Routing Errors | Delivery failed: A routing error occurred while attempting to deliver your message. This may be due to misconfigured mail servers or network issues. |
| Protocol Errors | Delivery failed: A protocol error occurred during communication with the recipient's mail server. Please ensure your message meets all technical requirements. |
| Authentication Failed | Delivery failed: Sender authentication was unsuccessful. Please check your sending domain's SPF, DKIM, or DMARC settings and try again. |
| Temporary Rejection | Delivery delayed: The recipient's server temporarily rejected the message. Our system will attempt to resend your email automatically. |
| Delayed | Delivery delayed: Your message could not be delivered immediately and will be retried. No action is required at this time. |
| Inactive Mailbox | Delivery failed: The recipient's mailbox is inactive or disabled. Please verify the recipient's email address or contact them for an updated address. |
| Bad Configuration | Delivery failed: There is a configuration issue with the recipient's mail server. The recipient may need to resolve this with their email provider. |
| Invalid Sender | Delivery failed: The sender address is invalid or not permitted by the recipient's server. Please check your sending address and domain settings. |
| Prohibited Attachment | Delivery failed: The message contains an attachment that is not allowed by the recipient's server. Please remove any prohibited files and try again. |
| Content Related | Delivery failed: The message was blocked due to its content, which may violate the recipient's policies. Please review your message and try again. |
| Relaying Issues | Delivery failed: Relaying issues prevented delivery to the recipient. This may be due to restrictions on the recipient's mail server. |
| Virus Related | Delivery failed: The message was blocked because a virus or malicious content was detected. Please scan your attachments and try again. |
| OOB | This message will include the specific reason for the OOB bounce, which may vary for each individual bounced message. |
subType: OOB
An Out-of-Band (OOB) Bounce occurs when an email server rejects a message after initially accepting it for delivery. Unlike immediate bounces, OOB bounces are triggered after the delivery process is completed. As a result, you may receive a bounced webhook after a delivered webhook for the same message.
type: Hard Bounce
All messages classified as Hard Bounce will not be retried and will be added to the suppression list. This process generates two webhook notifications: first, a bounced webhook, followed immediately by a suppressed webhook.
| subType | message |
|---|---|
| Hard Bounced | Delivery failed: The message could not be delivered. The recipient's address may not exist or is permanently unavailable. |
| Invalid Recipient | Delivery failed: The recipient's email address is invalid or does not exist. Please verify the address and try again. |
| Bad Domain | Delivery failed: The recipient's email domain does not exist or is misconfigured. Please check the domain and try again. |
| Admin Bounce | Delivery failed: The message was blocked by the recipient's administrator. Please contact the recipient for further information. |
| Rejection | Delivery failed: The message was rejected by the recipient's server, possibly due to policy or content restrictions. |
| Policy Related | Delivery failed: The message was rejected due to the recipient's email policy. Please review your message or contact the recipient. |
| Admin Bounced | Delivery failed: The message was blocked by an administrator on the recipient's side. Please contact the recipient for assistance. |
| Permanent Rejection | Delivery failed: The message was permanently rejected by the recipient's server. No further delivery attempts will be made. |
| Abuse | Delivery failed: The message was blocked due to an abuse complaint. Please ensure your message complies with email best practices. |
| Fraud | Delivery failed: The message was blocked due to suspected fraudulent content. Please review your message and ensure it is legitimate. |
| Spam Content | Delivery failed: The message was identified as spam and blocked by the recipient's server. Please review your content and try again. |
| Relay Denied | Delivery failed: The recipient's server denied relaying the message. This may be due to server restrictions or misconfiguration. |
| Spam Related | Delivery failed: The message was blocked due to spam-related reasons. Please ensure your message is not considered spam. |
| Spam Block | Delivery failed: The message was blocked by the recipient as spam. Please review your content and sending practices. |
| OOB | This message will include the specific reason for the OOB bounce, which may vary for each individual bounced message. |
subType: OOB
An Out-of-Band (OOB) Bounce occurs when an email server rejects a message after initially accepting it for delivery. Unlike immediate bounces, OOB bounces are triggered after the delivery process is completed. As a result, you may receive a bounced webhook after a delivered webhook for the same message.
type: Bounce
| subType | message |
|---|---|
| Integration Mode | Integration Mode: bounced webhook simulation. |
suppressed
Occurs when the recipient's address is added to the suppression list by our system.
{
"type": "suppressed",
"createdAt": "2025-11-28T06:29:57+00:00",
"messageId": "8814fd39-1ba7-4d94-bd4f-fbb2a85ea5ba",
"data": {
"id": "94d12dd9-f089-4afe-aee7-e28582015ba3",
"customerReference": "testing-integration-mode",
"suppressed": {
"message": "Integration Mode: suppressed webhook simulation."
}
}
}
unsubscribed
Occurs when the recipient unsubscribed by link or header from the email.
{
"type": "unsubscribed",
"createdAt": "2025-11-28T06:30:16+00:00",
"messageId": "13f91f81-a6ac-4350-ae3b-39e7a007fbde",
"data": {
"id": "be5bb4ee-0c72-4c0d-a56f-47de05790357",
"customerReference": "testing-integration-mode",
"unsubscribe": {
"unsubscribeType": "IntegrationMode",
"unsubscribeReason": "Integration Mode: unsubscribed webhook simulation."
}
}
}
complained
Occurs when the email is marked as spam by the recipient.
{
"type": "complained",
"createdAt": "2025-11-28T06:30:36+00:00",
"messageId": "334e5604-1ac7-49f6-863d-8165c970ed20",
"data": {
"id": "922f8131-a166-4b33-9666-196d82ba6537",
"customerReference": "testing-integration-mode"
}
}
failed
Occurs when the email failed to send due to an error.
{
"type": "failed",
"createdAt": "2025-11-28T06:36:18.8261187+00:00",
"messageId": "6014fb18-9afa-4612-9b4e-5889479be477",
"data": {
"id": "eb868cdd-4688-4f66-b61d-a2471d3ab0fe",
"customerReference": "testing-integration-mode",
"message": "Integration Mode: failed webhook simulation."
}
}
scheduled
Occurs when a scheduledAt email is queued for future delivery. See Scheduling Emails for details.
{
"type": "scheduled",
"createdAt": "2026-06-12T10:44:17+00:00",
"data": {
"scheduled": {
"scheduledAt": "2026-06-12T10:45:00+00:00",
"message": "Email is scheduled to be sent at June 12, 2026 at 10:45 UTC."
}
}
}