This section explains how to generate a valid certificate for Safari web push and how to configure it in admin UI.

Generate Safari web push certificate

  1. Log into your Apple Developer Console and select Certificates, Identifiers & Profiles.

    safari 1
  2. Select Identifiers from the menu on the left. Then select the + button.

    safari 2
  3. Select the Web Push IDs radio button. Then select the Continue button.

    safari 3
  4. Fill in the Description field and give your ID a unique identifier. Select the Continue button

    safari 4
  5. Double check your name and identifier (note down you identifier, you will need it for the website integration later) then register your Website Push ID.

    safari 5
  6. Select your newly made Safari Website Push ID.

    safari 6
  7. Create a new Production Certificate.

    safari 7
  8. Select Learn more > for instructions on how to generate a new certificate to upload. Select Choose File to upload your Certificate Signing Request (CSR) file if you have it saved locally.

    safari 8
  9. Download your new certificate. Double click to add this certificate to your Keychain. Right-click your certificate inside Keychain Access to export to a .p12 file.

    safari 9

    Double click to add this certificate to your Keychain. Right-click your certificate inside Keychain Access to export to a .p12 file.

    safari 10
  10. Add a password to your certificate during the export process. You will need to remember this password when you upload the .p12 file to the admin UI

    safari 11
  11. save the file to your local disk

Setup Safari in Admin UI

Please go into the Delivery console, open the "Apps" tab and add a new App.

Give your App a name, e.g. "My Safari App".

Then select the platform "Safari".

Upload an icon for the channel. This is only used inside the Push Admin so that you easier can recognize the channels by image.

Also it is required to use a Push template. This template is used to define the information that will be sent with the Safari Push.

At the end you will be asked for your:

  • Website name (required)

  • Allowed Domains (comma separated, no trailing slash, required)

  • URL template (required): This is used to contstruct the final notification URL. The URL to go to when the notification is clicked. Use %@ as a placeholder for arguments you fill in when delivering your notification. This URL must use the http or https scheme; otherwise, it is invalid. For example: as a URL template you can enter '' where '%@' is how you set placeholders.

  • Keystore (.p12) certificate

  • Keystore password

After successfully creating the App for Safari the following information will be automatically shown inside the App:

  • ApiUser: This is the API username.

  • Password: This is the password for the API user.

  • AccessToken: Instead of using username and password an Access Token is created.

  • platformId: The platform ID.

  • AppId: The App ID.

add safari app

After setting up the App now it is time to create Tags that users can register for.

Template and Payloads

Default template:

    "operation": "shift",
    "spec": {
      "title": "alertObj.title",
      "message": "alertObj.body",
      "url": "url-args"


Default payload before transformation:

  "title": "Default Title",
  "message": "This is the default message",
  "url": "url-argument-value"

Default payload after transformation:

  "alertObj" : {
    "title" : "Default Title",
    "body" : "This is the default message"
  "url-args" : "url-argument-value"

Message Object:









title of message





message text





A web URL



URL to open when clicking on notification

To learn more about how to create and modify JOLT templates please follow up in our developer documentation: push-templates