Apple Push Notification service

Connect Apple Push Notification service (APNs) to Push, for iPhone, iPad, Apple Watch, Apple TV and Mac apps.

APNs delivers notifications to your apps on iOS, iPadOS, watchOS, tvOS and macOS. Norbix signs each request to Apple with a .p8 auth key from your Apple developer account.

On our test stack the integration saves, but Test integration fails with The input is not a valid Base-64 string … for a key pasted as the form asks (with the -----BEGIN PRIVATE KEY----- lines). Sending through APNs could not be confirmed; the question is open in the docs program. Use Fake Push (Test Me) to try your flows meanwhile.

Get your credentials

You need a paid membership of the Apple Developer Program (individual or organization); sign in at developer.apple.com/account.

1. Team Id — Account → Membership details: the 10-character Team ID, e.g. 3VVDAGYR37 (Apple: locate your team ID).

2. App Bundle Identifier — Certificates, Identifiers & Profiles → Identifiers: the Identifier of your app, a reverse-domain string such as com.acme.shop. In Xcode it is on the app target's General tab (Bundle Identifier). It must match the app exactly, including case.

3. Key Id and .p8 key — Certificates, Identifiers & Profiles → Keys → the add button (+) → enter a Key Name, tick Apple Push Notifications service (APNs) → Continue → Register → Download. The file is AuthKey_<Key ID>.p8; the Key ID (e.g. CSWUWZ6VUU) is shown under the key name.

Apple lets you download a .p8 key once. If you lose it, revoke it and create a new key. One key serves every app of the team; you still create one integration per bundle id.

Connect it in Cloud

Where: Push → Integrations → Add New Integration → Apple Push Notification service → Connect · /projects/<project>/push/integrations/new/apns

Field	Required	What it does	Example
Team Id	yes	Your Apple developer team.	3VVDAGYR37
App Bundle Identifier	yes	The app that receives the notifications.	com.acme.shop
Key Id	yes	The id of the auth key.	CSWUWZ6VUU
Private key (.p8)	yes	The whole text of the .p8 file, from -----BEGIN PRIVATE KEY----- to -----END PRIVATE KEY-----. Encrypted on save and never shown again.	contents of AuthKey_CSWUWZ6VUU.p8
Production environment → Use Apple production APNs gateway	no	On = Apple's production gateway (App Store and TestFlight builds). Off = the sandbox gateway, for builds signed with a development profile.	off
Integration Name	yes	The name in your integrations list.	Acme iOS app (APNs)

The filled form (the key is made up for the docs).

Press Save. The page turns into Editing Apple APNs integration with the integration id (int_…) and the badges ENABLED, NOT TESTED, NOT CONFIRMED.

After save.

On the edit page Key Id and Private key (.p8) are empty: type both again when you change anything and press Save.

Test and set as default

Press Test integration at the bottom of the page — see Test an integration. A token from a development build works only with the sandbox gateway and a production token only with the production gateway; a correct key with the wrong switch looks exactly like a broken key. Then choose Actions → Set as default if campaigns should pick it — see Set an integration as default.

Common errors

Message	Cause	Fix
Could not send push via Apple Apn … The input is not a valid Base-64 string …	Seen on every test on our stack with a PEM key.	Open question; use the Fake provider meanwhile.
Required	An empty field — on edit also Key Id and the key.	Fill every field, type the secrets again.
BadDeviceToken (from Apple)	The token is from the other gateway (sandbox vs production), or not an iOS token.	Match the production switch to the build.
InvalidProviderToken (from Apple)	Wrong Team Id, Key Id or key.	Copy them again from the Apple developer account.