Skip to main content
Dugble tracks each SMS from queueing through its latest known provider or carrier outcome. Retrieve a message and inspect last_event for the current normalized state.

​
Statuses

Provider status support varies by route and destination. submitted or sent does not prove handset delivery.

​
Refresh provider status

For a submitted message with provider identifiers, you can request a provider status refresh:
The response contains the public SMS object with the latest normalized last_event value.

​
Failure information

For terminal failure states, the retrieve response can include a stable failure object:
Dugble exposes stable public failure codes for undelivered, rejected, failed, and expired messages. Use the code for application logic and the message for display or diagnostics.

​
Polling guidance

When polling message state:
  • Poll only messages that are not in a final state.
  • Apply backoff instead of polling continuously.
  • Stop polling after a final state is reached.
  • Use sync-status selectively because it performs a provider status lookup.

SMS events

Inspect the event history recorded for an individual SMS message.