This article describes what you need to consider when implementing your own mobile app using Smart ID Mobile SDK and you want to get push notifications triggered from Smart ID Digital Access component.
-
Your app must register its current device token together with a list of currently installed profile IDs (push IDs), using a Device registration API that you must implement in your organization's notification server. The mandatory data is described below.
-
Smart ID Digital Access component will post requests for all known profile IDs by using the Push API described below. This data can be used in push notifications and handled in your mobile app. This logic must also be implemented by your organization, both the notification server and the mobile app.
This image shows the communication between the mobile app, Smart ID Messaging and Smart ID Digital Access component.
Device registration API
Your organization's notification server must know the correlation between the profile ID (push ID) and the vendor and device ID. Therefore you must implement a Device registration API with the following details, which the app must provide:
-
profileID - this equals
pushIdin the Push API -
OS:iOSAndroid
-
deviceID:For iOS: device tokenFor Android: device registration token
For more information, see
-
For iOS: https://developer.apple.com/documentation/usernotifications
-
For Android: https://firebase.google.com/docs/cloud-messaging/server
Push API
Smart ID Digital Access component will send a REST (POST) request to your company's notification server with the following data which can be used in the push notifications: