An expired message is one the carrier could not deliver before its validity period ended, usually because the phone stayed off or out of coverage; it was attempted and is billed like a sent message.
Expiry is a final status distinct from failure. Nothing was wrong with the number or the content: the carrier accepted the message, stored it and retried, and the handset never became reachable before the validity period ran out. The usual causes are a phone that stayed switched off, a long stay out of coverage, or a SIM that sits in a drawer; depending on the operator, the same situation can instead come back as a failure with the reason absent subscriber. Expiry is common on old lists and in regions with intermittent coverage, and it shrinks when validity is longer for non-urgent content.
Because the message was handed to a carrier and attempted, it is billed like any sent message; the carrier generally charges for the attempt as well. It is billed once: the retries the network makes during the validity period add nothing.
Take a hypothetical delivery notice sent on Friday at 18:00 to a phone that is switched off until Sunday at 20:00. With a validity of 1,440 minutes it expires on Saturday at 18:00. With 2,880 minutes it expires on Sunday at 18:00, two hours too early. With 4,320 minutes it remains valid until Monday at 18:00, so it can be delivered when the phone comes back on Sunday evening.
Three mistakes are common:
- Resending an expired one-time code. Issue a new code instead; the old one is dead by design.
- Removing expired numbers as if they were unknown. The number exists; it was unreachable for a while.
- Counting expiries as route failures when comparing routes. Expiry usually reflects the phones rather than the route.
At SMSMeteor: expired is a final status of its own, separate from failed, meaning validity elapsed without delivery: 48 hours by default, settable per message up to 4,320 minutes. The message.expired webhook reports it, with expired_at. An expired message was sent, so it is billed once, at sent; the status definitions in the API reference list it with the others.
