Supported Events
At present, the Netcore Email API provides webhook support for a variety of events, including:
| Event | Description |
| Sent | Message has been sent successfully |
| Dropped | Message got dropped |
| Bounced | Message has hard bounce |
| Opened | Message got opened |
| Clicked | Recipient clicked a link in the message; will only occur when click tracking is enabled |
| Unsubscribed | Recipient Unsubscribed |
| Invalid | Syntactically incorrect email IDs |
| Abuse/Spam | Recipient marked the message as abuse/spam |
Each webhhok request can have a maximum of 100 events in a single HTTP POST request.
If you require higher batch (maximum 1000) Please reachout to support team at [email protected]
The following glossary and sample data outline each event, providing the specific parameters that were delivered through the HTTP POST:
| Parameters | Data Type | Events where this is meaningful/used | Description |
| TRANSID | Int64 | All | All assigns a Unique Transaction ID for each and every email which were sent |
| String | All | Recipient’s Email ID | |
| EVENT | String | All | Type of Event: sent/ dropped/ invalid/ bounced/ opened/ clicked/ unsubscribed/ spam |
| RESPONSE | String | sent/ dropped/invalid/ bounce | Response received from the end server like Delivery Logs, Bounce reason, reason for drop(blacklisted user / already unsubscribed) |
| X-APIHEADER | String | All | Information passed by you in the X-APIHEADER, during the time of email sent |
| TIMESTAMP | Int | All | Unix Timestamp of the occurrence of the event |
| USERAGENT | String | opened/ clicked/ unsubscribed/spam | User agent contains the detailed information about the browser from where a specific event in initiated. |
| IPADDRESS | String | opened/ clicked/unsubscribed/spam | IP address of the device from where the recipient has responded. |