What Protocols Does SMN Support?

SMN supports the following protocols:

• Email: Messages are sent to subscribers' email addresses by email.
• SMS: Messages are sent to subscribers' phone numbers by SMS message.

• HTTP or HTTPS: Messages are sent to subscription URLs by HTTP or HTTPS request. SMN only supports public network URLs and public IP addresses.
• FunctionGraph (function): Messages are used as payload to call functions.
• Voice notification: Messages are converted into voice messages and sent to the subscribed phone numbers. Only cloud services can send voice messages. Users cannot directly send voice messages.

  Voice subscriptions are available only in some regions of the Chinese mainland. Voice notification is not supported in Hong Kong, Macao, Taiwan, Xinjiang, and Tibet.

• DingTalk chatbot: Messages are sent to a DingTalk group through a DingTalk chatbot. You cannot @ someone in a group.
• WeCom chatbot: Messages are sent to a WeCom group through a WeCom chatbot. You cannot @ someone in a group.
• Lark chatbot: Messages are sent to a Lark group through a Lark chatbot. You cannot @ someone in a group.
  

  • Voice notification, DingTalk chatbot, WeCom chatbot, and Lark chatbot are in the open beta test (OBT). To use these protocols, 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.