APNs setup (.p8)
Upload your Apple push key so Pushlane can deliver to real devices.
#What you will need
| Value | Where to find it | Format |
|---|---|---|
| AuthKey_XXXXXXXXXX.p8 | Apple Developer → Keys (downloaded once) | PEM text file |
| Key ID | Shown on the key detail page and in the filename | 10 alphanumeric characters |
| Team ID | Top-right corner of every developer.apple.com page, and in Membership details | 10 alphanumeric characters |
| Bundle ID | Your app target → General → Bundle Identifier in Xcode | e.g. com.yourapp.ios |
#APNs key vs App Store Connect API key
These are two different Apple keys. Pushlane needs an APNs key, created in Certificates, Identifiers & Profiles → Keys with the Apple Push Notifications service (APNs) capability ticked.
Do not use a key from App Store Connect → Users and Access → Integrations. That key has an Issuer ID and cannot send push — APNs will reject every request with InvalidProviderToken.
| Key type | Where created | Has | Can send push? |
|---|---|---|---|
| APNs key | developer.apple.com → Certificates, Identifiers & Profiles → Keys | Key ID + .p8 | Yes |
| App Store Connect API key | App Store Connect → Users and Access → Integrations | Key ID + Issuer ID + .p8 | No — InvalidProviderToken |
#Create the APNs key in Apple Developer
Sign in at developer.apple.com with your paid developer account.
- Go to Certificates, Identifiers & Profiles → Keys and click the + button (or Create a key).Heads upThis is developer.apple.com, not App Store Connect.
- Give the key a name (e.g. Pushlane Push Key), then tick Apple Push Notifications service (APNs). That checkbox is what makes this a real push key.
- Click Configure next to APNs. Set the Environment (Production covers both production and sandbox when used with auth-key tokens; choose Production unless you have a specific reason to scope to sandbox only). Optionally restrict the key to a specific App ID. Click Save.
- Click Continue then Register. On the confirmation page:
- Copy the Key ID (10 characters) — it is also in the filename.
- Click Download to get
AuthKey_XXXXXXXXXX.p8. Apple only lets you download it once. Store it securely — this is what Pushlane will use to sign APNs tokens.
- Your Team ID is displayed in the top-right corner of every developer.apple.com page and under Account → Membership details.
#Upload to Pushlane
Open the Pushlane dashboard and go to Settings → APNs (or complete step 5 of the Quickstart if you haven't finished it yet).
- Paste your Team ID (10 chars).
- Paste your Key ID (10 chars — from the .p8 filename or key detail page).
- Enter your app's Bundle ID (e.g.
com.yourapp.ios). - Click Choose your AuthKey_XXXXXX.p8 and select the file. The key is read in your browser and encrypted at rest on upload — it is never stored or shown in plaintext again.
- Click Save credentials.
#Verify a real push
Once you have uploaded your key and the SDK is wired (device token registered):
- In the Quickstart or Settings → Install SDK, click Send a test push.
- Pushlane runs the event through the real ingest pipeline. The panel reports whether the event was accepted, ingested, and whether Apple accepted the APNs token.
- Check your physical device — the push should appear within a few seconds.
If the push does not arrive, check in order:
- Did you add the Push Notifications capability to your Xcode target? Without it the device never produces a token (see the iOS Quickstart → step 2).
- Is the Team ID correct and does it match the account that owns the Bundle ID?
- Is the Key ID the one from the APNs key (not an App Store Connect key)?
- Does your device have notification permissions enabled for the app (iOS Settings → Notifications)?
#Next step
Your push credentials are live. Head to the flow builder to compose your first automated push campaign — triggers, delays, branches, and push nodes on a visual canvas.