Although you can use oAuthService API and pushService API for both simple and rich messages, there is one major difference between the two. When creating rich messages, you must use the Push Rich Content API first before using another API to send the message. For simple messages, this additional step is not required.
For information about REST APIs, see the REST API Methods page in https://developer.ibm.com.
Examples
Simple API
Use the following APIs:
oAuthService API
This post is not that helpful in that it doesn’t say what the actual difference between the two is, or if there are any advantages of using one over the other (such as one offers more features), or how to chose between the two. The documentation page for rich content: https://developer.ibm.com/customer-engagement/docs/watson-marketing/ibm-engage-2/watson-campaign-automation-platform/rest-api-methods/create-rich-content-api/ includes things like video. Does this mean the notification can contain video? We understood that a notification can only contain a title, message, and action. We know simple message can also have an icon, but this is undocumented unfortunately.
This post is not that helpful in that it doesn’t say what the actual difference between the two is, or if there are any advantages of using one over the other (such as one offers more features), or how to chose between the two. The documentation page for rich content: https://developer.ibm.com/customer-engagement/docs/watson-marketing/ibm-engage-2/watson-campaign-automation-platform/rest-api-methods/create-rich-content-api/ includes things like video. Does this mean the notification can contain video? We understood that a notification can only contain a title, message, and action. We know simple message can also have an icon, but this is undocumented unfortunately.