Push Notification Credentials
For the Atomic platform to deliver push notifications to your apps, you'll need to configure credentials for each relevant platform.
Add and manage notification platforms here, so your customers can receive native mobile notifications, then continue to the SDK guide to dive complete the configuration for iOS, Android, Flutter, React Native, or Cordova.
Add push notification credentials
You must have access to the Notification Platform resource to be able to add notification credentials. See more in Workbench members
- Open the Atomic Workbench, navigate to 'Configuration' and under SDK select 'Notifications'. Alternatively, open the command palette, type Notifications and select Configuration > Notifications.
- Click 'New platform', and select either
iOSorAndroid.
- Enter the required information to register the corresponding platform:
For iOS
- You have two configuration options:
iOSandiOS Sandbox. TheiOS Sandboxconfiguration is for development purposes and is applicable only to apps installed via Xcode build. For apps distributed via TestFlight or the App Store, theiOSconfiguration is required. - For
iOS Sandbox, you can use either the Apple Sandbox Push Service Certificate or the Apple Push Services Certificate. However, for theiOSconfiguration, only the Apple Push Services Certificate is suitable. - Certificate Authentication: you'll require your app's bundle ID, a P12 export of your push notification certificate and private key, and the password for the P12 export if applicable.
- Token Authentication: you'll require your apps bundle ID, a p8 export of your signing key, a signing key id and a team identifier.
For Android
You'll need to configure FCM HTTP v1 before proceeding. You can then configure the FCM credentials in Atomic via API, or by using the Workbench as below by providing your App Id, a paltform token and other required details (the API guide may still be a handy reference even if you are configuring these settings in the workbench):
