Step 5: Review the key configuration, then select Confirm.

Step 4: Under Key Services, select APNs, then select Continue. Step 3: Under Key Description, enter a unique Name for the key. Step 2: In the sidebar, select Keys, and then select add (+). Step 1: In your Apple Developer Account, navigate to Certificates, Identifiers & Profiles To create a private key for APNs, complete the following: Generate the authentication token and download it as a.There are two main steps involved in retrieving a token signing key and uploading it to Swrve: For more information, see the Apple help article Communicate with APNs using authentication tokens. We recommend using token-based authentication for all new apps and transitioning existing apps to token-based authentication when possible. Token signing keys never expire, unlike iOS push certificates.The signing key works for both sandbox and production environments.You can use one token to distribute notifications for all of your company’s apps.There are other advantages to token-based authentication: Apple’s token-based authentication offers a faster way to communicate with APNs than certificate-based connections.

For more information about managing push notifications in Swrve, see Intro to push notifications. Once Swrve has a copy of your authentication token or push certificate, we can send messages to your users on your behalf.

Swrve now supports using either an authentication token or TLS certificate with APNs. To send a push notification to an iOS user, Apple requires an authentication token (.p8 file) or TLS certificate (.p12 file) that you must provide in the Integration settings screen of your app. Swrve uses the Apple Push Notification service (APNs) to send push notifications to iOS devices (iPhone, iPad).

Apple sandbox push services