Learn how to activate Alibaba Cloud Short Message Service (SMS), complete compliance approval, and send your first message. Includes estimated timelines for each step.
Key information at a glance
Important timelines
-
Total integration time: 10 to 15 business days, including carrier registration.
-
Earliest sending time: 3 to 5 business days after qualification, signature, and template approval.
-
Stable sending in production: Carrier registration must be complete (7 to 15 business days).
Transparent pricing
-
OTP and notification messages start at CNY 0.045 per message. Promotional messages start at CNY 0.055 per message.
-
Messages over 70 characters are split and billed as multiple messages. Domestic SMS Pricing | International SMS Pricing.
-
SMS resource package quota is consumed first. After exhaustion, pay-as-you-go billing applies.
Limitations
-
Mobile originated (MO) messages can only be received through callbacks, not queried via the API or console.
-
Promotional messages cannot be sent from 20:00 to 8:00.
-
Per-number rate limit:
-
OTP: up to 1 message per minute, 5 per hour, and 10 per day.
-
Notification and promotional messages: up to 50 messages per day.
-
Workflow
Each SMS message consists of an SMS signature and an SMS template. Apply for a qualification, signature, and template before sending. Use template variables to customize message content.
This workflow applies to Domestic SMS. For International SMS, check the corresponding console pages.
Carrier registration typically takes 7 to 10 business days but can take longer, as carriers do not provide a guaranteed timeframe. Apply for qualifications and signatures well in advance to ensure carrier registration completes before you go live.
|
Step |
Description |
Supported methods |
|
① Prepare your account |
Register an Alibaba Cloud account, complete identity verification, and activate SMS. To use the API, also create an AccessKey pair. Important Under the current identity verification requirements for SMS signatures, the self-use qualifications of individual accounts cannot pass the signature filing. Individual users must use the SMS Authentication product or upgrade to an enterprise account. |
Console: Activate SMS |
|
② Apply for a qualification |
Submit application: Domestic SMS requires qualification documents for the signature's owning entity, per Ministry of Industry and Information Technology (MIIT) and carrier regulations. Apply before creating a signature or template. Review guidelines | How-to guide |
Console: Domestic Messages - Qualification Management API: SubmitSmsQualification | QuerySmsQualificationRecord | QuerySingleSmsQualification |
|
Wait for review: SMS signature applications require an approved qualification. Due to high application volume, review may be delayed. Approval typically takes up to 2 business days. Review hours: 9:00 to 21:00, Monday to Sunday. Reviews are postponed during public holidays. |
||
|
③ Apply for an SMS signature |
Submit application: An SMS signature identifies the sender. Use your entity's name or an authorized name. Recommended: name of your enterprise or public institution. Review guidelines | How-to guide |
Console: Domestic Messages - Signature Management API: CreateSmsSign |
|
Wait for review: You can apply for an SMS template only after your SMS signature is approved. The review is typically completed within 2 hours. Review hours: 9:00 to 21:00, Monday to Sunday. Reviews are postponed during public holidays. |
Console: Domestic Messages - Signature Management API: GetSmsSign | QuerySmsSignList Delivery report: SignSmsReport |
|
|
Carrier registration: New signatures are automatically submitted after approval. For existing signatures, check status and submit manually on the Signature Management page. Messages sent with unregistered signatures will be blocked by carriers. How-to guide Carrier registration time: 7 to 10 business days or longer. Important
Before registration is complete, messages may fail to send. The following error code may be returned:
|
||
|
④ Apply for an SMS template |
Submit application: An SMS template defines message content. Types: OTP, notification, and promotional. Templates consist of variables and static content — use variables according to specifications. Review guidelines | How-to guide |
Console: Domestic Messages - Template Management API: CreateSmsTemplate |
|
Wait for review: You can send messages only after the SMS template is approved. The review is typically completed within 2 hours. Review hours: 9:00 to 21:00, Monday to Sunday. Reviews are postponed during public holidays. |
Console: Domestic Messages - Template Management API: GetSmsTemplate | QuerySmsTemplateList Delivery report: TemplateSmsReport |
|
|
⑤ Send messages |
Use an approved signature and template to send messages to your target users. Important
Before bulk sending, wait until signature registration status is |
Console: Batch Sending | How-to guide API: SendSms | SendBatchSms |
|
⑥ Check sending details |
Get message sending results: Check the status of sent messages. Statuses include sent, failed, and awaiting delivery report. |
Console: Batch Sending | Business Statistics API: QuerySendDetails Delivery report: SmsReport (HTTP push mode | Message Queue mode) |
|
View user replies: Query the content of mobile originated (MO) messages from users. |
Delivery report: SmsUp (HTTP push mode | Message Queue mode) |
|
|
⑦ Set up alerts |
Set up contacts and configure alerts to protect service stability. Recommended alerts: OTP abuse prevention, SMS resource package remaining quota, message volume, and message sending frequency. How-to guide |
Console: Contact Settings | Security Settings | Sending Frequency Settings |
Try the service
|
You can log on to the console and go to the Quick Start & Delivery Test page. In the Delivery Test section, you can quickly send a test message. You must apply for an SMS signature and an SMS template and wait for them to be approved. After you bind a test number, you can use the message sending feature. Send test message
Note
|
The test page offers two modes: Send test message via API and Send test message via Console. Bind up to five test phone numbers. Select the [Custom] Signature/Template type, choose an approved signature and template, then click Send Message via API. |
Sending methods
Console
- Send SMS messages using the console
If you prefer an interactive UI, you can use the console to create message content, send messages, and query statistics.
API
- Send SMS messages using an API
If you prefer to code, you can use the API or SDK to send messages.
Review rules
Message results
SMS provides multiple ways to retrieve message sending status, user replies, and signature/template review status.
The following table uses Domestic SMS as an example. For International SMS, see the console for available features.
|
Information type |
Console |
API |
Delivery report |
|
Signature review status |
GetSmsSign output parameter QuerySmsSignList output parameter |
||
|
Template review status |
GetSmsTemplate output parameter QuerySmsTemplateList output parameter |
||
|
Message sending status |
QuerySendDetails output parameter |
||
|
Mobile originated (MO) message |
Not supported |
Not supported |
Dedicated DingTalk group
SMS provides a dedicated DingTalk group for submitting signatures and templates, viewing statistics, and receiving alerts. Activate it at Domestic Messages Settings - DingTalk Group Settings.
This feature is available only for Domestic SMS. For detailed instructions, see Dedicated DingTalk groups for Short Message Service.