Apple
Guide to configuring Apple Push Notification Service (APNs) credentials in Recurly Engage for push prompts.
The Apple integration lets Recurly Engage send push notifications to iOS and tvOS devices through the Apple Push Notification service (APNs).
Available on all Recurly Engage subscription plans
Prerequisites
- You must have Company or App Administrator permissions in Recurly Engage.
- Your app must integrate the Recurly Engage software development kit (SDK) on the target platform.
Limitations
- Supported on Android devices and web browsers with FCM support.
Definition
The APNs connector ingests your Apple Push credentials (Bundle ID, Team ID, Token Key, and Key ID), so Recurly Engage can authenticate and send push notifications through APNs.
Key benefits
Native iOS delivery
Reach iPhone, iPad, and Apple TV clients with rich notifications.
Secure token-based authentication
Use modern JSON Web Token (JWT) keys to avoid expired certificates.
Centralized management
Store and rotate your APNs keys within Recurly Engage.
Key details
Required information
Provide the following under Settings > Push Credentials in Recurly Engage:
- APNs Bundle ID: Your app's Bundle Identifier.
- APNs Team ID: Your Apple Developer Team Identifier.
- APNs Token Key: The private key file (
.p8) generated in Apple Developer. - APNs Token Key ID: The Key ID associated with your
.p8file.
Get your APNs credentials
1
Log in to the Apple Developer Console
Log in to the Apple Developer Console.
2
- Give your key a name.
- After creation, download the
.p8file. - Record the Key ID (displayed next to your key name).
Once you've imported the credentials, toggle your APNs credentials to Active in Recurly Engage to begin sending push prompts to iOS and tvOS users.
Updated 4 days ago
Did this page help you?