Skip to main content
Dugble records delivery events as an email moves through the sending pipeline. Events are useful for troubleshooting delivery and understanding how the latest message status was reached.

List message events

Retrieve events for a message with:
For example:
The response contains the events associated with that message.

Pagination

Email events use offset pagination: The event response does not include a has_more field. Advance offset by the number of events returned when you need the next page.

Event data

An event can include a unique event ID, event type, occurrence time, provider, and optional code or message.

Events and message status

The email resource exposes last_event as the latest known state. Use the event list when you need the history behind that state. For example, a message may move from queued to processing, then submitted, and finally delivered.

Real-time processing

If your application needs to react automatically to delivery changes, use webhooks instead of continuously polling message events. See Webhooks for event delivery to your application.