Simple Message Notification
Simple Message Notification
- 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
On this page
Show all
What Protocols Does SMN Support?
Updated on 2023-03-20 GMT+08:00
SMN supports the following protocols:
- HTTP or HTTPS
Messages are sent to subscription URLs by HTTP or HTTPS request. SMN only supports public network URLs and public IP addresses.
- DingTalk chatbot
Messages are sent to a DingTalk group through a DingTalk chatbot. You cannot directly address someone in a group with the @ symbol.
- WeCom chatbot
Messages are sent to a WeCom group through a WeCom chatbot. You cannot directly address someone in a group with the @ symbol.
- Lark chatbot
Messages are sent to a Lark group through a Lark chatbot. You cannot directly address someone in a group with the @ symbol.
NOTE:
- DingTalk chatbot, WeCom chatbot, and Lark chatbot are in the open beta test (OBT). To use these functions, submit a service ticket to apply for the OBT.
- After the OBT is enabled, your token will be invalid. You need to log in to the console again to use the token. When calling an API, you need to obtain a new token.
- The number of WeCom, DingTalk, and Lark messages that can be sent is limited, and the recipient system may be faulty. As a result, messages may fail to be sent.
In this case, SMN does not ensure successful message delivery.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.