A rejected message was refused by the gateway before sending (invalid number, unsupported destination, blocked content) and costs nothing; a failed message was accepted by a carrier that then could not deliver it, and is billed.
The distinction is about where the message stopped. Rejection happens at the gateway, before anything leaves, usually in the response to the request itself, with an error you can act on at once: fix the number, drop the destination, change the text. Failure happens later, at the carrier, after the message was handed over, and comes back with a carrier code: unknown subscriber, barred, filtered, network error. Both are final states in the message status lifecycle, but they mean opposite things for the bill.
| Status | Where it stops | What comes back | Billed |
|---|---|---|---|
| rejected | At the gateway, before sending | An error, in the API response or the import report | Never |
| failed | At the carrier, after sending | A carrier code and a reason, with the delivery receipt | Yes, it was attempted |
Billing follows the attempt. A rejected message never reached a carrier, so there is nothing to pay; a failed one did, and carriers generally charge for the attempt whether or not it ends on a handset.
Suppose a hypothetical batch of 1,000 messages in which 12 numbers are malformed. The response lists those 12 as rejected, each with its error, and queues the other 988. Later, 40 of the 988 fail as unknown subscribers. The bill covers the 988 messages that were sent, the 40 failures included, and nothing for the 12 rejections.
Two mistakes are common:
- Resubmitting rejected messages unchanged. They will be refused again; fix the input first.
- Resending to numbers that failed as unknown subscribers. The attempt fails again and is billed again.
At SMSMeteor: rejected rows are listed in the import report or returned individually in batch responses with their reason, and are never billed; only a malformed batch request is refused as a whole. A message.rejected webhook reports each refusal, with its reason. Failed messages were handed to a carrier, so they are billed, and they carry carrier_code and a plain-English failure_reason.
