Safari Website Notifications


Safari Web Push notifications integration is described in Web Push SDK 3.0 Guide

To configure Safari push notifications, follow these simple steps:

1. Registering with Apple

1.1. To send push notifications,first register in Certificates, Identifiers & Profiles section of Member Center.

1.2. Registration requires an iOS developer license or Mac developer license.

1.3. Add a new certificate.

1.4. Choose Website Push ID Certificate and click Continue.

1.5. To register, enter the following information:

Identifier (Website Push ID). Your unique reverse-domain string, such as (must start with web.).

Website Push ID Description. The name used throughout the Provisioning Portal to refer to your website. Use it to label your Website Push IDs into a more human-readable format for your own convenience.

1.6. Afterwards, download the push notification certificate.


The certificate you download from Apple is a .cer file. To get the .p12 file necessary to configure Pushwoosh, you must export a private key. See Exporting Private Key part of the iOS Configuration Guide.

2. Configure the Safari section in your Pushwoosh Control Panel

Website Name: name of your website that will be displayed in the notification title.

Allowed domains: an array of websites allowed to request permission from user, one domain per line.

URL Template: target URL to go to when the notification is clicked. Use %@ as a placeholder for arguments you fill in when delivering your notification. This URL spelling must contain http or https; otherwise, it is invalid.

Website Icon: upload your website icon to Pushwoosh. The icon must be 256×256 pixels, Pushwoosh will automatically resize it for all other UIs.

Key file: upload the .p12 certificate file that you downloaded in step 1.6.

Private key password: input the certificate password.

The push package with the icon set, website JSON dictionary and manifest file, that Safari requests from the server will be automatically generated by Pushwoosh, and you can download it whenever you need.


When a user is asked for permission to receive push notifications, Safari asks your web server for a push package. The package contains data used by the notification UI, such as your website name and icon, as well as a cryptographic signature that verifies that your notification is coming from a trusted source: you. Push package with all its content is downloaded ONLY ONCE by each subscribed user upon registration, and cannot be force-updated on devices. Consider this when launching Safari push notifications for your website in production.