• 228 destinations
  • No KYC, ever
  • Bitcoin, Monero, USDT and 4 more

Delivery and reporting

Message status lifecycle

The message status lifecycle is the forward-only sequence an SMS moves through at a gateway: queued, sent, then delivered, failed or expired, or rejected when refused before sending.

A message is queued once it has been accepted and priced, and may wait there for its send time, its delivery window or its turn in a paced campaign. It becomes sent when it is handed to a carrier, which is the billing point. From there it reaches one final state: delivered on a handset receipt, failed when the carrier could not deliver it, or expired when the validity period ran out. Rejected is the sixth state, for messages refused before any attempt, which are never billed.

StatusWhat it meansBilled
queuedAccepted and priced, waiting for its time, window or turnNot yet
sentHanded to a carrierYes, at this point
deliveredThe handset confirmed receiptAlready, at sent
failedThe carrier could not deliver; a reason is attachedYes, it was sent
expiredThe validity period ran out before deliveryYes, it was sent
rejectedRefused before sendingNever

Statuses move forward only. Webhook events can arrive late, be retried or be replayed, so an earlier status must never overwrite a later one; handlers therefore apply events by status rank rather than by arrival time, with final states above sent and sent above queued. Hypothetically, a reminder created at 08:59 for a window opening at 09:00 is queued, then sent at 09:00:01, then delivered at 09:00:05. If the delivered event reaches your endpoint first and a retried sent event follows, the record must stay delivered.

Two misreadings are common:

  • Treating sent as the end of the story. It is final only in countries that give carrier acknowledgement and no handset receipts.
  • Counting rejected as a delivery failure. Nothing was sent, so nothing was billed, and the fix is in the input; see failed vs rejected.

At SMSMeteor: the six statuses are queued, sent, delivered, failed, expired and rejected; test keys return a seventh, test, for messages that were validated and priced but never sent or billed. Signed webhook events follow each status change: message.sent, message.delivered, message.failed, message.expired and message.rejected. The API reference defines each status.

Go further

See the term in practice.An email address opens the account, the rate card is public, payment is crypto, the test key is free.
Start sending