Domestic SMS API error codes

Error code

Error message

Description

isv.SMS_SIGNATURE_SCENE_ILLEGAL

The signature and template types are inconsistent.

Cause: The template type does not match the signature type. Incorrect example: You used a verification code signature to send a notification message or promotional message.

Solution: Signatures are categorized into two types: Verification Code and General. Templates are categorized into three types: Verification Code, Notification Message, and Promotional Message. Verification Code signatures can only be used to send messages using Verification Code templates. General signatures can be used to send messages using all types of templates. We recommend changing the signature type to General.

isv.EXTEND_CODE_ERROR

Invalid extension code. The same extension code cannot be used with multiple signatures.

Cause: The same extension code was used with different signatures.

Solution: When you call the API to send messages, use a different extension code for each signature.

isv.SIGN_STATE_ILLEGAL

The signature status is "Unavailable".

Cause: You cannot use a signature in the "Unavailable" status to send messages.

Solution: Check the signature status details and modify the signature according to the reason for its "Unavailable" status.

isv.DOMESTIC_NUMBER_NOT_SUPPORTED

International/Hong Kong, Macao, and Taiwan message templates do not support sending messages to numbers in the Chinese mainland.

Cause: International/Hong Kong, Macao, and Taiwan message templates only support sending to international numbers and numbers in Hong Kong, Macao, and Taiwan.

Solution: To send messages to the Chinese mainland, apply for a domestic message template.

isv.DENY_IP_RANGE

The region of the source IP address is blocked.

Cause: The system detected that the source IP address is from a region outside the Chinese mainland.

Solution: Use a source IP address from the Chinese mainland. IP addresses from international regions or Hong Kong, Macao, and Taiwan are prohibited from being used to send messages to the Chinese mainland. For more information, see service endpoint.

isv.DAY_LIMIT_CONTROL

The daily sending limit is reached.

Cause: The daily message sending limit that you set in the console has been reached.

Solution: To modify the limit, log on to the Short Message Service console and go to the General Settings > Domestic Message Settings > Security Settings page to modify the daily sending limit.

isv.MONTH_LIMIT_CONTROL

The monthly sending limit is reached.

Cause: The monthly message sending limit that you set in the console has been reached.

Solution: To modify the limit, log on to the Short Message Service console and go to the General Settings > Domestic Message Settings > Security Settings page to modify the monthly sending limit.

isv.SMS_CONTENT_ILLEGAL

The message content contains prohibited content.

Cause: The message content contains prohibited content.

Solution: Modify the message content. For more information, see Message template specifications.

isv.SMS_SIGN_ILLEGAL

The signature is prohibited from use.

Cause: The signature is prohibited from use.

Solution: Apply for a compliant signature in the Short Message Service console. For more information, see Apply for a message signature.

isp.RAM_PERMISSION_DENY

Insufficient RAM permission.

Cause: The RAM permission is insufficient.

Solution: Grant the AliyunDysmsFullAccess (administrative permissions) to the RAM user associated with the current AccessKey. For more information, see Authorize a RAM user.

isv.OUT_OF_SERVICE

The service is suspended.

Cause: The service is suspended due to an insufficient account balance. For more information, see Overdue payments.

Solution: Top up your account.

isv.PRODUCT_UN_SUBSCRIPT

This Alibaba Cloud account is not subscribed to any Cloud Communication products.

Cause: The account associated with the AccessKey has not subscribed to Cloud Communication services, such as Short Message Service, Voice Service, or Data Service.

Solution: Ensure that Short Message Service is activated for the account associated with the current AccessKey.

isv.PRODUCT_UNSUBSCRIBE

The product is not activated.

Cause: The account associated with the AccessKey has not subscribed to the product that corresponds to the API. For example, this error occurs if a user who has activated only Short Message Service calls a Voice Service API.

Solution: Check whether the account associated with the AccessKey has subscribed to the service that corresponds to the API. To activate a service, see Short Message Service or Voice Service.

isv.ACCOUNT_NOT_EXISTS

The account does not exist.

Cause: An incorrect account name or AccessKey was used.

Solution: Confirm your account information.

isv.ACCOUNT_ABNORMAL

The account is abnormal.

Cause: The account is abnormal.

Solution: An error occurred when the system queried the billing service. Click the link and scan the QR code with DingTalk to join the exclusive DingTalk group for Short Message Service.

isv.SMS_TEMPLATE_ILLEGAL

The template content does not match the template parameters.

Cause:

• The specified template code is incorrect.

• The specified template content or format is incorrect.

Solution:

• Check whether the AccessKey and the template belong to the same account.

  If they belong to the same account, log on to the Short Message Service console and check whether the template is approved on the Template Management page. Use the template only after it is approved.

• Check the format of the template parameters. For more information, see Message template specifications.

  • Ensure that the TemplateCode parameter does not contain spaces.

  • Ensure that the variables specified in the TemplateParam parameter match the variables for the template identified by the TemplateCode parameter.

  • Ensure that the value of the TemplateParam parameter is a JSON string.

  • Ensure that the number of variables specified in the TemplateParam parameter is the same as the number of variables in the template.

  • Ensure that the names of variables specified in the TemplateParam parameter are the same as the names of variables in the template.

isv.SMS_SIGNATURE_ILLEGAL

The specified signature cannot be found in your account.

Cause:

• The specified signature is not found. This issue may occur because the AccessKey and the signature belong to different accounts, or you are using a signature that has not been approved.

• The specified signature may contain spaces, question marks, or typos that make it invalid.

isv.INVALID_PARAMETERS

Invalid parameter format.

Cause: A parameter is in an invalid format.

Solution: Check the parameter format in the relevant API reference.

For example, the date format for the SendDate parameter in the QuerySendDetails API operation is yyyyMMdd. A correct value is 20170101. An incorrect value is 2017-01-01.

isp.SYSTEM_ERROR

A system error occurred. Please try again.

Cause: A system error occurred.

Solution: Call the API operation again.

isv.MOBILE_NUMBER_ILLEGAL

Invalid mobile number format.

Cause: The mobile number is in an invalid format.

isv.MOBILE_COUNT_OVER_LIMIT

The number of mobile phone numbers specified in the PhoneNumbers parameter exceeds the limit.

Cause: The number of mobile numbers specified in the PhoneNumbers parameter exceeds the limit.

Solution:

• Ensure the number of mobile numbers is within the specified limit.

• The limits on the PhoneNumbers parameter for different API operations are as follows:

  • SendSms and SendCardSms: up to 1,000 mobile numbers per request.

  • SendBatchSms and SendBatchCardSms: up to 100 mobile numbers per request.

isv.TEMPLATE_MISSING_PARAMETERS

A value is not assigned to a template variable.

Cause: In the TemplateParam parameter, not all variables are assigned a value.

Solution: Use a JSON-formatted string to assign values to the template variables. For example, if the template is Hello, ${name}, your appointment is confirmed. Your appointment number is ${code}, you can set the TemplateParam parameter to {"name":"Tom","code":"123"}.

isv.BUSINESS_LIMIT_CONTROL

The throttling limit of Cloud Communication is triggered.

Cause: You have reached the message sending frequency limit of Cloud Communication.

Solution:

isv.INVALID_JSON_PARAM

Invalid parameter format. Change the value to a string.

Cause: The parameter is in an invalid format. The value is not a valid JSON string.

Solution: Specify a valid JSON-formatted string for the TemplateParam parameter, such as {"code":"123"}.

isv.BLACK_KEY_CONTROL_LIMIT

Blocklist control.

Cause: The phone number is on a blocklist. Such numbers have a history of unsubscriptions or complaints. For example, the user has filed a complaint or unsubscribed from messages on platforms such as 12321. Promotional messages cannot be sent to these numbers. Numbers on the blocklist cannot be removed.

Solution: Avoid sending promotional messages to this number.

isv.PARAM_LENGTH_LIMIT

The parameter value exceeds the length limit.

Cause: The parameter value exceeds the length limit.

Solution: For notification message templates created after January 10, 2018, variables are limited to 1 to 35 characters in length. For verification code templates, variables are limited to 4 to 6 characters in length. Modify the parameter length to comply with these limits.

For more information about template specifications, see Message template specifications.

isv.PARAM_NOT_SUPPORT_URL

URLs are not supported in variables.

Cause: The variable contains restricted content. For example, URLs are not allowed in variables.

Solution: Check whether you are passing URLs or sensitive information in variables. For information about template content specifications, see Message template specifications.

isv.AMOUNT_NOT_ENOUGH

Insufficient account balance.

Cause: The account balance is insufficient.

Solution:

• Top up your account. Before you send messages, refer to Pricing for messages sent to the Chinese mainland and Pricing for messages sent to international regions and Hong Kong, Macao, and Taiwan to confirm that your account balance (including the remaining quota in any purchased packages) is sufficient to cover the expected number of messages. Otherwise, messages may fail to be sent.

• The purchased package must match the message destination region.

  Incorrect example: If you use a purchased Singapore package to send messages to Thailand, the messages will fail.

For more information about billing and package purchases, see Billing overview.

isv.TEMPLATE_PARAMS_ILLEGAL

The specified variable content does not match the attribute type selected for the variable when the template was created.

Cause: The value provided for a variable with the "Phone Number" attribute is not a valid phone number.

Solution: The value of the phone variable must be a standard 5- to 11-digit mobile or fixed-line number in the Chinese mainland. For more information about variable attributes, see Variable attribute specifications for verification code templates or Variable attribute specifications for notification templates.

SignatureDoesNotMatch

The signature generated by the client does not match the signature on the server.

Cause: A signature encryption error occurred.

InvalidTimeStamp.Expired

The timestamp or date has expired.

Cause: A timestamp error is usually caused by time zone differences. The time the request is sent and the time the server receives it differ by more than 15 minutes.

Solution: Use GMT.

SignatureNonceUsed

The signature nonce has been used.

Cause: The value for SignatureNonce has already been used. The SignatureNonce parameter specifies a unique random number to prevent network replay attacks.

Solution: Use a different random number for each request.

InvalidVersion

Invalid API version.

Cause: The version number (Version) is incorrect.

Solution: Confirm the API version number. The API version (Version) for Short Message Service is 2017-05-25.

InvalidAction.NotFound

The specified API could not be found. Check your URL and method.

Cause: The API name specified in the Action parameter is incorrect.

Solution: Use the correct API endpoint and name in the Action parameter.

isv.SIGN_COUNT_OVER_LIMIT

The daily limit for signature applications has been reached.

Cause: The number of signature applications in a single day exceeds the limit.

Solution: Plan your daily signature applications and apply again the next day. For more information, see Differences between individual users and enterprise users.

isv.TEMPLATE_COUNT_OVER_LIMIT

The daily limit for template applications has been reached.

Cause: The number of template applications in a single day exceeds the limit.

Solution: Plan your daily template applications and apply again the next day. For more information, see Differences between individual users and enterprise users.

isv.SIGN_NAME_ILLEGAL

The signature name does not comply with specifications.

Cause: The signature name does not comply with the specifications.

Solution: Apply for the signature again. For information about the specifications, see Message signature specifications.

isv.SIGN_FILE_LIMIT

The size of the signature verification file attachment exceeds the limit.

Cause: The size of the signature verification file attachment exceeds the limit.

Solution: Compress the signature verification materials to under 2 MB.

isv.SIGN_OVER_LIMIT

The number of characters in the signature exceeds the limit.

Cause: The number of characters in the signature name or application reason exceeds the limit.

Solution: Modify the signature name or application reason and resubmit it for review. For information about signature specifications, see Message signature specifications.

isv.TEMPLATE_OVER_LIMIT

The number of characters in the template exceeds the limit.

Cause: The number of characters in the template name, content, or application reason exceeds the limit.

Solution: Modify the template name, content, or application reason and resubmit it for review.

SIGNATURE_BLACKLIST

The signature content contains non-compliant information.

Cause: The signature content contains non-compliant information.

Solution: Modify the signature content. For information about signature specifications, see Message signature specifications.

isv.SHORTURL_OVER_LIMIT

The daily limit for short URL applications has been reached.

Cause: The number of short URLs that are created in a single day exceeds the limit.

Solution: Plan your daily short URL applications and create them again the next day.

isv.NO_AVAILABLE_SHORT_URL

No valid short URL is available for this account.

Cause: The enterprise customer does not have a valid short URL.

Solution: The enterprise customer must apply for a new valid short URL and make sure that the API for generating short URLs is called within the validity period of the short URL.

isv.SHORTURL_NAME_ILLEGAL

The short URL name cannot exceed 13 characters in length.

Cause: The short URL name exceeds 13 characters in length.

Solution: Recreate the short URL based on the requirements.

isv.SOURCEURL_OVER_LIMIT

The original URL exceeds the character limit.

Cause: The original URL exceeds the character limit.

Solution: Make sure that the character length of the original URL meets the requirements.

isv.SHORTURL_TIME_ILLEGAL

The validity period of the short URL exceeds the limit.

Cause: The specified validity period of the short URL exceeds the 30-day limit.

Solution: Make sure that the validity period of the short URL is within 30 days.

isv.PHONENUMBERS_OVER_LIMIT

The number of uploaded phone numbers exceeds the limit.

Cause: The number of phone numbers uploaded in a single API call exceeds the 50,000 limit.

Solution: Call the API for generating short parameters multiple times. Make sure that no more than 50,000 phone numbers are uploaded in a single API call.

isv.SHORTURL_STILL_AVAILABLE

The short URL generated from the original URL is still valid.

Cause: The short URL generated from the original URL is still valid and does not need to be recreated.

isv.ERROR_EMPTY_FILE

The signature file is empty.

Cause: The signature file is empty.

Solution: Check the signature file and upload screenshots of relevant documents, such as qualification certificates and letters of authorization. For more information, see Apply for a message signature.

isp.GATEWAY_ERROR

Failed to call the sending application module.

Cause: Failed to call the sending application module.

Solution: An error occurred when the system called the sending application module. Try to send the message again.

isv.ERROR_SIGN_NOT_DELETE

A signature that is under review cannot be deleted.

Cause: The signature is under review and cannot be deleted.

Solution: Delete the signature after the review is complete.

isv.ERROR_SIGN_NOT_MODIFY

An approved signature cannot be modified.

Cause: An approved signature cannot be modified.

Solution: Apply for a new signature that complies with the specifications. For more information, see Apply for a message signature.

isv.ERROR_TEMPLATE_NOT_DELETE

A template that is under review cannot be deleted.

Cause: The template is under review and cannot be deleted.

Solution: Delete the template after the review is complete.

isv.ERROR_TEMPLATE_NOT_MODIFY

An approved template cannot be modified.

Cause: An approved template cannot be modified.

Solution: Submit a new template application that complies with the specifications. For more information, see Message template specifications.

isv.SMS_OVER_LIMIT

You can apply for a maximum of 100 templates or signatures per day.

Cause: You have exceeded the daily limit of 100 applications for templates or signatures.

Solution: Wait 24 hours before you apply again, or click the link and scan the QR code with DingTalk to join the exclusive DingTalk group for Short Message Service for assistance.

isv.CUSTOMER_REFUSED

The user has unsubscribed from promotional messages.

Cause: The user has unsubscribed from promotional messages.

Solution: Respect the user's preference and stop sending promotional messages to this user.

isv.SMS_TEST_SIGN_TEMPLATE_LIMIT

Test template and signature restrictions.

Cause: Test-only signatures and test-only templates must be used together.

Solution: Use the test-only signature and test-only template provided by Short Message Service. For more information, see Send a test message.

isv.SHORTURL_DOMAIN_EMPTY

Failed to create a short URL.

Solution: Submit the top-level domain of this link for registration.

template_parameter_count_illegal

Verification code templates support only one variable for the verification code.

Cause: Only one parameter can be defined as a variable in a verification code template.

Solution: Modify the variables in the verification code template. For more information, see Specifications for verification code templates.

isv.SMS_TEST_TEMPLATE_PARAMS_ILLEGAL

The variable in a test-only template must be a 4- to 6-digit number.

Solution: When you use a test template, the variable must be a 4- to 6-digit number.

isv.SMS_TEST_NUMBER_LIMIT

Messages can be sent only to bound phone numbers.

Cause: The recipient phone number for the test message is not bound in the console, or the binding process is incomplete or has not taken effect.

Solution:

• To send messages by using the test feature, you must bind a test phone number.

• Ensure the binding is complete and has taken effect, as system synchronization may be delayed.

Cause: The phone number specified in the API request does not match the bound phone number.

Solution: Check whether the phone number specified in the API request or console call exactly matches the test phone number that is bound in the console, including the country or region calling code and format.

Cause: If you encounter this error code in a production environment, you may have confused the test environment with the production environment.

Solution: Test signatures and templates, which are marked with a green "Test" tag in the console, must be used to send messages only to bound test numbers. Make sure that you use non-test signatures and templates to send messages in the production environment.

isv.SMS_SIGN_EMOJI_ILLEGAL

Signatures cannot contain emojis.

Solution: Emojis are not supported in signatures.

isv.SECURITY_FROZEN_ACCOUNT

Your account has been inactive for a long period of time. For security purposes, message sending from your account is restricted.

If you want to continue to use this account, contact your business manager.

IS_CLOSE

The channel was shut down when the message was being sent.

Alibaba Cloud automatically removes closed channels. We recommend that you try again later.

PARAMS_ILLEGAL

Invalid parameters.

Check whether parameters such as the message signature, message content, and phone number are correctly specified.

MOBILE_NOT_ON_SERVICE

Service suspended, non-existent number, service paused, powered off, or out of service area.

Cause: The carrier returned an abnormal real-time status for the number, such as powered off, service suspended, non-existent number, service paused, or out of service area.

Solution: Verify that the recipient's phone number is in a normal state.

MOBILE_SEND_LIMIT

The daily or monthly sending limit for a single number is exceeded, the throttling limit is exceeded, or the frequent sending limit is exceeded.

To prevent malicious use of the platform and a large number of message sending requests in a short period of time, both Alibaba Cloud and carriers have implemented throttling limits.

MOBILE_ACCOUNT_ABNORMAL

User account abnormal, mobile number portability, or overdue payments.

We recommend that you check the number's status and try again after you make sure that the status is normal.

MOBILE_IN_BLACK

The phone number is on the blocklist.

The phone number is in the carrier's blocklist database. This may be because the user has unsubscribed from messages that use this signature or the number matches the carrier's blocklist rules.

MOBLLE_TERMINAL_ERROR

Mobile terminal issue, full memory, full SIM card, or illegal device.

Check the device's status and the blocklist of any mobile security software. Then, try again after restarting or changing the device.

CONTENT_KEYWORD

Content keyword blocking.

Cause: The carrier automatically blocks messages based on keywords that pose potential risks or have high complaint rates.

Solution: Check the message content and modify it.

INVALID_NUMBER

Abnormal number status.

Cause: The recipient's number status is abnormal. For example, the phone is powered off, the service is suspended, the number is non-existent, the service is paused, the phone is out of the service area, or the number is in an invalid format.

Solution: Verify that the number status is normal and the format is correct.

CONTENT_ERROR

The content does not have an unsubscribe option.

Cause: Promotional messages must include unsubscribe information.

Solution: Check the message content and add unsubscribe information. Add "Reply R to unsubscribe" at the end of the promotional message. For more information, see Specifications for promotional message templates.

REQUEST_SUCCESS

The request is successful, but the platform has not received the delivery receipt from the carrier.

Cause: The status of the recipient is abnormal.

Solution: Check whether the recipient status is normal.

SP_NOT_BY_INTER_SMS

International messaging is not activated.

Cause: The recipient has not activated the feature of receiving international messages.

Solution: Contact the carrier to activate the international messaging feature before you send messages.

SP_UNKNOWN_ERROR

Unknown carrier error.

This error code indicates that the delivery receipt that Alibaba Cloud received from the carrier reports an unknown error. Alibaba Cloud periodically checks with the provider for updates.

USER_REJECT

The recipient unsubscribed from this service, or the product is not activated.

We recommend that you remove such recipients from the sending list.

NO_ROUTE

No channel is available for the current message content.

The business scenario is not supported.

isv.UNSUPPORTED_CONTENT

Unsupported message content.

Cause: The message content includes unsupported content, such as Traditional Chinese characters, emoji, or other special characters (for example, 【】〖〗『』「」m² • ①★※→ ❤™).

Solution: Check the message template content and the specified variable values. Modify the message content and remove the unsupported characters or symbols. For more information about template and variable specifications, see Message template specifications.

isv.SMS_CONTENT_MISMATCH_TEMPLATE_TYPE

The message content does not match the template attributes.

Cause: You cannot use a notification template to send promotional or marketing content.

Solution: Use a promotional message template to send the message. "Reply R to unsubscribe" must be added at the end of the template.

isv.ONE_CODE_MULTIPLE_SIGN

One extension code corresponds to multiple signatures.

Cause: The specified extension code and signature do not match the signature that is historically associated with the extension code.

Solution: Make sure that the signature that corresponds to an extension code remains consistent during sending, or update the extension code-to-signature mapping with the new signature. For more information, see Manage extension codes.

isv.CODE_EXCEED_LIMIT

The number of self-extended extension codes exceeds the limit.

Cause: The limit for self-extended extension codes is 10ⁿ, where n is the number of digits for self-extended codes, which varies by user. After the limit is exceeded, new extension codes cannot be assigned for sending messages with new signatures.

Solution: We recommend that you contact your product operations manager to modify the number of digits for self-extended extension codes, or delete recyclable mappings between extension codes and signatures. For more information, see Manage extension codes.

isv.CODE_ERROR

The specified extension code is unavailable.

Cause: The number of digits in the specified self-extended extension code exceeds the limit. The code cannot be used to send messages.

Solution: Specify an extension code of the standard length.

PORT_NOT_REGISTERED

The current port number has not completed the enterprise real-name registration process.

Cause: Message content providers are required to file real-name qualification information. If the filing is not completed on some carrier gateways, messages may be blocked.

Solution: Complete real-name registration before you send messages. We recommend following the instructions in Real-name registration guide. You can log on to the Short Message Service console and go to the Signature Management page to check the registration status of your signature. The carrier real-name registration process typically takes 7 to 10 business days. However, carriers do not guarantee this timeline, and the process may take longer.

isv.SIGN_SOURCE_ILLEGAL

Unsupported signature source.

Cause: An unsupported signature source was used when the signature was created or modified.

Solution: Select a compliant signature source.