API Integration Security
Tenant-Specific API Endpoints
Automation Studio API
Fire an Entry Event
Single-Send Journeys
SMS Status Codes
Bulk Data Ingest API
REST Reference
API Call Volume History and Health
This table includes status codes returned from MobileConnect API calls for all locations. Use these codes to evaluate and troubleshoot your SMS sends.
| Code | Status | Definition |
|---|---|---|
| 1000 | QueuedToSfmcSendService | The message was added to the Marketing Cloud Engagement message sending service queue. |
| 1500 | QueueFailureToSfmcSendService | A failure occurred when attempting to add the message sending service queue. You can try to send the message again later. |
| 1501 | ValidationError | A validation error occurred. You can try to send the message again later. |
| 2000 | DeliveredToAggregator | The message was delivered from Marketing Cloud Engagement to a downstream delivery partner (aggregator). This status doesn’t necessarily indicate that the message was delivered to the recipient. The status is updated when we receive a delivery confirmation from the mobile carrier or device. For shared codes, this status is the final one. |
| 2500 | FailedToAggregator | An error occurred when sending the message from Marketing Cloud Engagement to the downstream aggregator. You can try to send the message again later. |
| 2501 | UnknownToAggregator | The downstream aggregator experienced an error while processing the message. |
| 2502 | FailedToAggregatorDueToInvalidDestinationAddress | The downstream aggregator couldn’t deliver the message because the destination phone number invalid. |
| 2600 | ThrottledToAggregator | The downstream aggregator couldn’t accept the message because too many requests were received simultaneously. Marketing Cloud Engagement automatically attempts to re-send messages that were throttled in this way. If you see this status in your logs, it means that our attempts to re-send the message were unsuccessful. |
| 2601 | SocketExceptionToAggregator | The downstream aggregator couldn’t accept the message because of a connection error. Marketing Cloud Engagement automatically attempts to re-send messages that fail in this way. If you see this status in your logs, it means that our attempts to re-send the message were unsuccessful. |
| 3000 | Enroute | The message is in the process of being delivered to the recipient’s mobile carrier. |
| 3001 | SentToCarrier | The message was sent to the recipient’s mobile carrier but hasn’t been accepted yet. |
| 3002 | AcceptedByCarrier | The message was accepted by the recipient’s mobile carrier but hasn’t been delivered yet. |
| 3400 | Unknown | An unknown error occurred. |
| 4000 | Delivered | The message was delivered to the recipient’s device. |
| 4500 | Undeliverable | The message wasn’t delivered to the recipient’s device. |
| 4501 | Expired | The message wasn’t delivered and has exceeded the maximum delivery time. This issue can occur when the recipient’s device isn’t connected to a mobile network or is otherwise unreachable. |
| 4502 | Deleted | The message wasn’t delivered and has been deleted by the carrier. |
| 4503 | Rejected | The message was rejected by the recipient’s mobile carrier. This issue can occur when the carrier determines that the message is spam or other abusive content. |
| 4504 | FailedDueToUnknownSubscriber | The message wasn’t delivered because the carrier couldn’t find the subscriber. |
| 4505 | FailedDueToInvalidDestinationAddress | The message wasn’t delivered because the destination phone number was invalid. |