Skip to main content

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

  1. Open the Atomic Workbench, navigate to 'Configuration' and under SDK select 'Notifications'. Alternatively, open the command palette, type Notifications and select Configuration > Notifications.
Workbench view of creating a push notification credential
Add a new push notification credential
  1. Click 'New platform', and select either iOS or Android.
Workbench view of creating a push notification credential
Add a new push notification credential
  1. Enter the required information to register the corresponding platform:

For iOS​

Workbench view of creating a push notification credential for iOS
Add a new push notification credential for iOS
  • Platform: You have two configuration options: iOS and iOS Sandbox. The iOS Sandbox configuration is for development purposes and is applicable only to apps installed via Xcode build. For apps distributed via TestFlight or the App Store, the iOS configuration is required.
  • App Id: Your iOS App Id.
  • Authentication Type: Use a push certificate or a token to implement notifications.
  • Authentication configuration:
    • Token Authentication: A team identifier, your app's bundle ID, a signing key id and the p8 export of your signing key.
    • Certificate Authentication: The password for the P12 export if applicable and a P12 export of your push notification certificate and private key. Note: For iOS Sandbox, you can use either the Apple Push Notification service SSL (Sandbox) or the Apple Push Notification service SSL (Sandbox & Production). However, for the iOS configuration, only the Apple Push Notification service SSL (Sandbox & Production) will work.

See the SDK guide for instructions on setting up push notifications on iOS in the Atomic SDK.

For Android​

You need to have configured FCM HTTP v1 before proceeding. You can then configure the FCM credentials in the Atomic workbench (or via API) by providing:

  • Platform: FCM HTTP V1.
  • Application Id: Your Android Application Id.
  • Service account private key: The contents of your Firebase service account private key file (JSON).
  • Send data-only notifications (optional): whether or not to populate the notification option as documented by Firebase - when disabled (default) the notification will be sent with the title and body as configured in the card notification settings and the optional Channel Id value as configured in the Android settings. In most cases this setting should be left disabled.
  • Channel Id (optional): maps to the android_channel_id option as documented by Firebase.
  • Restricted package name (optional): maps to the restricted_package_name option as documented by Firebase.

See the SDK guide for instructions on setting up push notifications on Android in the Atomic SDK.

Workbench view of creating a push notification credential for Android
Add a new push notification credential for Android via the Workbench
Last updated on