![]() To register a specific device ID to be used as a recipient address for notifications, you can use the REST API. You can look up the device IDs registered with a mobile app in the Device Registry, from the Notifications page for the associated backend in the UI. The device ID changes periodically, but this is handled internally and is transparent to the mobile app. Multiple instances of the same mobile app on the same device have different device IDs. After that point, the ID can be used to identify that specific recipient. This ID is used to ensure that notifications are sent to the correct recipient.Ī unique device ID is assigned when a mobile app registers a device during the device handshake. The device ID, also known as the notification token, uniquely identifies the specific instance of a mobile application associated with a specific device. The notification is received by the mobile application, and the owner of the device gets it. The notification is addressed to the associated device IDs and distributed to the appropriate push networks for delivery. You can use this ID to cancel a message if it hasn’t been sent yet. When you POST a notification, an ID is created for the message. You can send the notification immediately or schedule it to be sent at a later date and time. You can send the notification to a specific user or device or set of users or devices, to everyone in the backend, or to a specific device type (Android, iOS or Windows). You compose a notification, for example, "Hi! Our storewide sale is tomorrow," and define a recipient for it. The steps below summarize the path that a notification takes. ![]() Once your mobile app is configured and installed on a device, it connects to its backend to receive notifications. ![]() As a mobile application developer, you configure your mobile app to receive notifications over the network. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |