The notification data can also be sent by using the REST client using
URL arguments as part of the SAP Mobile Platform push endpoint,
or as the delivery address URL. The use of embedded arguments in the URL is not
supported.
All URL arguments (zero to many) are optional. The arguments are converted into
APNS/GCM/BES/BIS/WNS/MPNS notifications as explained:
http[s]://<host:port/Notification>/<application connection ID>?alert=<alert>&badge=<badge>&sound=<sound>&data=<data in text format>
- APNS
Parameters |
Description |
alert |
Text of the alert message. |
badge
|
Number that appears as the badge on the application icon.
|
sound
|
Name of the sound file in application bundle. |
data
|
Custom payload data values. These values must use the
JSON-structured and primitive types, such as dictionary
(object), array, string, number, and boolean. |
- GCM
Parameters |
Description |
alert |
An arbitrary string (such as "Updates Available") that
collapses a group of like messages when the device is
offline, so that only the last message is sent to the
client. |
data
|
Payload data, expressed as parameters prefixed with data
and suffixed as the key. |
- BIS/BES
Parameters |
Description |
data
|
Notification data |
alert |
Text of the alert message |
badge
|
Number that appears as the badge on the application
icon |
- WNS
Parameters |
Description |
alert |
The text of the alert message to be sent as a Tile
notification |
badge |
Number that appears as the badge on the application
icon |
data |
Payload data to be sent |
- MPNS (Notification for Windows Phone)
Parameters |
Description |
alert |
The text of the alert message to be sent as a Tile
notification |
badge |
Number that appears as the badge on the application icon
|
data |
Payload data to be sent |
Based on the data send either in headers or in the URL, corresponding
notification is sent to the device:
Header|Notification |
Tile Notification |
Toast Notification |
Raw Notification |
Alert |
Yes |
Yes |
No |
Badge |
Yes |
No |
No |
Data |
No |
No |
Yes |