- What's New
- Function Overview
- Service Overview
- Getting Started
-
User Guide
- Topic Management
- Subscription Management
- Message Template Management
- SMN Operation Recording
- Logs
- Permissions Management
- Quotas
- Appendix
- API Reference
- SDK Reference
-
FAQs
- What Are the Advantages of SMN?
- What Protocols Does SMN Support?
- How Is SMN Billed?
- What Are the Requirements for an SMN Topic Name?
- How Many Topics Can I Create?
- How Many Subscriptions Can Be Added to a Topic?
- How Many Messages Can Be Published to a Topic?
- How Many Message Templates Can I Create?
- What Are the Limitations on SMS Messages?
- Can I Add Subscriptions Using Multiple Protocols to a Topic?
- Can a Topic Creator Change Subscription Protocols in a Topic?
- Can I Change a Subscription Endpoint for a Topic?
- Can I Delete a Published Message?
- Does SMN Ensure That Messages Are Received by Subscription Endpoints?
- Will a Subscriber Receive the Same Message Multiple Times?
- Why Do Subscribers Fail to Receive Messages After I Publish Messages to a Topic?
- What Can I Do When Pictures in an Email Message Cannot Be Displayed?
- How Do I Obtain My Account ID?
- How Does DingTalk, Lark, or WeCom Chatbot Obtain Subscription Endpoints?
- Videos
Show all
Overview
Welcome to the Simple Message Notification API Reference. Simple Message Notification (SMN) is a reliable and flexible large-scale message notification service. It enables you to efficiently send messages to phone numbers, email addresses and HTTP/HTTPS servers and connect cloud services through notifications, reducing system complexity.
This document describes how to use application programming interfaces (APIs) to perform operations in SMN, such as creating, querying, deleting, and updating resources. For details about all supported operations, see API Overview.
Before you use SMN by calling APIs, please get yourself familiar with basic SMN concepts. For details, see Service Overview.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
