Safari Push Notifications

Connect Safari Push Notifications to Push, for website notifications in Safari on macOS.

Safari Push Notifications reach the visitors of your website in Safari on macOS. Norbix signs each request with your Website Push ID certificate (a .p12 file) from Apple.

On our test stack the integration saves, but Test integration fails with A temporary internal error occurred and a reference id. Sending through Safari Push could not be confirmed; the question is open in the docs program.

Get your credentials

You need a paid membership of the Apple Developer Program.

1. Certificates, Identifiers & Profiles → Identifiers → + → Website Push IDs → enter a description and an identifier such as web.com.acme.shop → Register.

2. Certificates → + → Website Push ID Certificate → pick the Website Push ID → upload a certificate signing request → download the certificate and open it in Keychain Access.

3. In Keychain Access, export the certificate with its private key as a .p12 file with a password.

4. Turn the file into base64 in one line, for example base64 -i webpush.p12 on a Mac. Do not re-wrap or re-type the output.

The certificate expires (usually after a year), and nothing warns you — note the renewal date.

Connect it in Cloud

Where: Push → Integrations → Add New Integration → Safari Push Notifications → Connect · /projects/<project>/push/integrations/new/safari-push

Field	Required	What it does	Example
Website Push Id	yes	The id you registered with Apple.	web.com.acme.shop
Certificate (.p12) base64	yes	The base64 text of the .p12 file. Encrypted on save.	MIIK…
Certificate password	yes	The password of the .p12 file. Encrypted on save.	••••••••
Integration Name	yes	The name in your integrations list.	Acme website (Safari)

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

Press Save. The page turns into Editing Safari Push integration with the badges ENABLED, NOT TESTED, NOT CONFIRMED; the certificate and password are not shown again.

After save.

Test and set as default

Press Test integration at the bottom of the page — see Test an integration. Then choose Actions → Set as default if campaigns should pick it — see Set an integration as default.

Common errors

Message	Cause	Fix
A temporary internal error occurred. Reference: ref_…	Seen on every test on our stack.	Open question; give the reference to support.
Required	An empty field — on edit also the certificate and password.	Fill every field again.