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: Use the OauthServiceURL: https://apiX.ibmmarketingcloud.com/oauth/token
  • Push to Contact API: https://api2.silverpop.com/restdoc/#!/channels/push_to_contacts_post_9 (simple + inbox or inbox only message)

    • oAuthService API

  • Rich Content API: https://api2.silverpop.com/restdoc/#!/channels/createRichContentSet_post_12
  • Push to Contact API: https://api2.silverpop.com/restdoc/#!/channels/push_to_contacts_post_9


    • 2 comments on"How are APIs for simple mobile app push messages different from rich mobile app push message APIs?"

    1. john June 06, 2019

      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.

      Reply
    2. johnL June 06, 2019

      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.

      Reply

    Join The Discussion

    Your email address will not be published. Required fields are marked *