Skip to main content
Dugble records delivery events as an SMS moves through the sending pipeline and the downstream provider reports delivery outcomes.

List message events

Retrieve events for a message with:
For example:

Pagination

SMS event history currently supports a limit parameter only. Unlike Email events, SMS events do not currently expose an offset parameter in the service contract.

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 SMS resource exposes last_event as the latest known state. Use the event list when you need the delivery history behind that state. Common SMS states include queued, processing, submitted, sent, delivered, undelivered, rejected, failed, expired, unknown, and canceled.

Refresh provider status

When you need the latest state directly from the provider, Dugble also exposes POST /sms/{message_id}/sync-status for messages that have already been submitted to a provider.

Real-time processing

For applications that need to react automatically to delivery changes, use webhooks instead of repeatedly polling message events. See Webhooks for event delivery to your application.