This topic helps you quickly identify, diagnose, and resolve errors with Alibaba Cloud Short Message Service (SMS). It covers error codes for the entire message lifecycle, from API calls and message delivery to delivery receipts. It also provides corresponding actionable solutions.
Error code classification
This document is extensive. You can use Ctrl+F (or Command+F) to search for a specific error code.
To pinpoint issues accurately, you must understand the different types of error codes that occur during the message lifecycle.
Common error codes: Returned in the HTTP response when you call an API, such as
SendMessageToGlobe. These codes indicate issues with the request itself (for example, invalid parameters and insufficient permissions), or that the platform rejected the request.Delivery receipt status codes: Returned after the platform accepts the message, either through an asynchronous callback or by calling the
SmsReportAPI. These codes reflect the final delivery result from the carrier to the recipient's device, such as succeeded, failed, or blocked.SMPP error codes and message states: Available only when you use the Short Message Peer-to-Peer (SMPP) protocol. They indicate the result of an SMPP command or the final status of a message, in compliance with the SMPP Protocol Specification V3.4.
Common error codes
Error code | SMPP error code | Description | Solution |
OK | 20 | The request was successful. | - |
INVALID_SENDERID | 25 | The sender ID is invalid or unapproved. |
|
FORBIDDEN_ACTION | 26 | Your account's API call permissions have been downgraded. | Submit a ticket to restore the API call access. |
OUT_OF_SERVICE | 27 | The SMS service is suspended. | - |
ACCOUNT_NOT_EXISTS | 29 | The account does not exist. | Activate SMS and complete identity verification. |
SMS_CONTENT_CODE_ILLEGAL | 31 | The message template is invalid, does not exist, or has been rejected. | Log on to the SMS Console. In the left navigation pane, select . Check the approval status. If the status is Rejected, click Create Template. |
SMS_SIGN_NAME_ILLEGAL | 32 | The signature is invalid, does not exist, or has been rejected. | Log on to the SMS console. In the left navigation pane, select . Check if the signature passed exactly matches the approved one. If the status is Rejected, review the reason and apply for a new signature. |
MOBILE_NUMBER_ILLEGAL | 33 | The mobile phone number format is incorrect. | Verify the phone number format and resubmit the request. |
MOBILE_COUNT_OVER_LIMIT | 34 | The number of mobile phone numbers exceeds the limit of 1,000. | The BatchSendMessageToGlobe operation supports up to 1,000 recipients per request. Split larger lists into multiple requests. |
CONTENT_MISSING_PARAMETERS | 35 | A value is missing for a variable in the message template. | Check the |
INVALID_PARAMETERS | 36 | One or more parameters are invalid. | Check your parameter configuration to ensure all values are correct. |
INVALID_JSON_PARAM | 42 | A parameter is empty, or the JSON string could not be parsed. | Check your parameter configuration to ensure all values are correct. |
PARAM_LENGTH_LIMIT | 44 | The length of a template variable value exceeds the limit. |
|
AMOUNT_NOT_ENOUGH | 45 | Your account has an insufficient balance or resource package. | Purchase a resource plan or top up your balance. |
SYSTEM_ERROR | 46 | An internal system error occurred. | A temporary error occurred on the Alibaba Cloud platform. Try again later. If the problem persists, submit a ticket and provide the RequestId. |
DATA_NOT_EXIST | - | The queried message record does not exist. | Try again later. |
QPS_LIMIT_CONTROL | 48 | The QPS limit for message sending was reached. | Reduce your API call frequency to stay within your account's QPS limit. |
ONLINE_BILLING_FAILED | 49 | Online billing failed, or an internal system error occurred. | The online billing system is busy. Try again later. |
QUERY_DATE_ILLEGAL | 52 | The query time range is invalid. | Check your parameter configuration to ensure all values are correct. |
RAM_PERMISSION_DENY | 55 | Resource Access Management (RAM) verification failed due to insufficient permissions. | Grant the RAM user the required permissions to call the API and try again. |
PRODUCT_NOT_SUBSCRIBED | 57 | SMS is not activated. | Log on to the SMS console and activate the service. |
SMS_SECURITY_INTERCEPTED | 61 | The message was blocked by a risk control policy. | - |
SMS_CONTENT_ILLEGAL | 62 | The message content is noncompliant. | Ensure that your message content complies with all applicable laws and regulations. |
ACCOUNT_ILLEGAL | 63 | Your account has been blacklisted for sending noncompliant content. | - |
BLACK_KEY_CONTROL_LIMIT | 64 | A variable in the message content contains a blacklisted keyword. | The variable's value triggered a platform security policy. Review and modify any sensitive or noncompliant content in the variable. |
NOT_SUPPORTED_COUNTRY | 65 | Sending messages to this country or region is not supported. | - |
SENDERID_BLACKLISTED | 67 | A risk control policy blocked the sender ID. | - |
IMDA_COMPANY_REQUIRE_LOA | 68 | The sender ID must be registered with the Infocomm Media Development Authority (IMDA). | Register your sender ID with the IMDA. |
SYSTEM_LIMIT_CONTROL | 81 | The daily sending limit for the system is reached. | - |
FREQUENCY_LIMIT_DAY | 83 | The daily sending limit for a single number is reached. | In the console, go to and reset the daily sending limit for a single number. Default limit: 20 messages per day. |
ALERT_LIMIT_DAY | 84 | The daily sending limit for your account was reached. | In the console, go to and reset the daily limit. |
ALERT_LIMIT_MONTH | 85 | The monthly sending limit for your account was reached. | In the console, go to and reset the monthly limit. |
COUNTRY_TRAFFIC_LIMIT | 86 | The daily sending limit for a specific destination country or region was reached. | In the console, go to and reset the daily sending limit for that destination. |
CONTENT_EXCEED_LIMIT | - | The message content exceeds the 512 KB size limit. | Reduce the message size to be within the 512 KB limit. |
QUANTITY_INCONSISTENT | - | The number of recipients (in the | Ensure that the number of recipients matches the number of messages. |
Specified AccessKeyId is not found | - | The specified AccessKeyId does not exist. | Check that the AccessKeyId configured in your code is correct, valid, and has not been disabled. |
Delivery receipt status codes
Status code | SMPP error code | Description |
success | 0 | The message was sent successfully. |
IN_SMS_CONTENT | 201 | The message content or length is invalid. |
INVALID_NUM | 202 | The recipient's phone number is invalid. |
INVALID_SENDERID | 203 | The sender ID is invalid. |
OPERATOR_NOT_SUPPORT | 204 | The carrier does not support the phone number. |
PHONE_NOT_AVAILABLE | 205 | The phone number or recipient device is unavailable, or the device's storage is full. |
PORTED_NUM | 206 | The carrier for the phone number has changed. |
RECEIVER_BLACKLIST | 207 | The recipient's number is on a carrier blacklist. |
SYSTEM_ERR | 208 | A carrier system error occurred. |
SP_UNKNOWN_ERR | 209 | The message delivery failed for an unknown reason. |
URL_FAILURE | 210 | A URL in the message content is on a blacklist. |
expired | 211 | The message could not be delivered because the recipient's device was turned off or out of service for an extended period. |
NO_VALID_SUPPLIER | 212 | No IMDA-compliant carrier is available for Singapore. |
SMPP message states
SMPP message state | Final message state | Description |
DELIVERED | DELIVRD | Message delivered to destination. |
EXPIRED | EXPIRED | Message validity period has expired. |
DELETED | DELETED | Message has been deleted. |
UNDELIVERABLE | UNDELIV | Message is undeliverable. |
ACCEPTED | ACCEPTD | Message is in accepted state. |
UNKNOWN | UNKNOWN | Message is in invalid state. |
REJECTED | REJECTD | Message is in a rejected state. |
For more information, see SMPP Protocol Specification V3.4.