Skip to content
Skip to main content

Send events

The Send events endpoints show what happened to every message you send through Transactional send and Agent Accounts: accepted, delivered, bounced, marked as spam, or rejected, for each recipient.

Use them to:

  • Find out why a message didn't reach a recipient, with the bounce reason and the response from the recipient's mail server.
  • Track your delivery, bounce, and complaint rates over time, and get a health grade for the last 7 days.
  • Find which sending domain, Agent Account, or recipient domain is causing bounces or complaints.

For real-time events, use webhooks. These endpoints are for reviewing patterns and trends over time, and for debugging the delivery of individual messages after they're sent. They aren't for following each message as it happens. Avoid polling them for new events. The delivered, bounced, complaint, and rejected events are the same outcomes that the Agent Account notifications (message.delivered, message.bounced, message.complaint, message.rejected) and the Transactional send notifications (message.transactional.*) report. Subscribe to those to act on each message, and use Send alerts to find out when a rate crosses a threshold. See Use webhooks for real-time events.

Events are kept for 90 days, and metrics cover up to a year. Sends from connected grants (Google, Microsoft, and other providers) aren't included. These endpoints use your application's API key.

For examples, see Monitor delivery and engagement.