Message Apple Wallet pass holders

Once a user adds your Apple Wallet pass, Pushwoosh registers it as an Apple Wallet platform subscription tied to that User ID. Passes live on iPhone and Apple Watch.

You can reach holders in several ways: send a one-time push, send a pass update, automate messages from a Customer Journey, or notify holders of a specific pass via API.

Send a one-time push to pass holders

Send a standalone push to one pass holder or to a wider audience. It appears as a lock-screen message on the pass.

1. Open the one-time push composer. Either click Send message in Campaigns → Wallet Passes → Apple Wallet, or go to Campaigns → One-Time Messages and click Send message → One-time push.

2. On the Content step, write the message or select a preset.

3. On the Audience step, set who receives the message. The default depends on where you opened the composer:

   • From Send message on a pass: Send to specific users is selected, and Recipients (User IDs) already lists that pass holder’s User ID. Send as is to reach that one holder, or change the audience:
     • Add more User IDs in Recipients (User IDs)
     • Switch to Send to segment
     • Choose Send to all subscribers
   • From One-Time Messages: Set the audience as in a regular one-time push: Send to specific users, Send to segment, or Send to all subscribers.

4. Under Target platforms, select Apple Wallet.
5. Send or schedule the message.

Примечание

When you target a segment, delivery goes to users in that segment who have the Apple Wallet platform registered, not to everyone who saved a specific pass.

Send a pass update

Editing a pass and saving re-signs it and notifies every device that added it. iOS fetches the new version in the background. To alert holders about a specific change, set a Change message on the field so iOS shows it on the lock screen.

1. In Campaigns → Wallet Passes → Apple Wallet, find the pass and click Edit in the actions menu.
2. Change the fields you need, and add a change message to any field you want holders to be alerted about.
3. Click Save.

Every device that added the pass receives the update. Fields without a change message update silently.

Automate messages from a Customer Journey

Send messages automatically based on events or segments.

Trigger-based entry journey

Developer assistance needed

Sending custom events requires your developer team to integrate the postEvent API call into your backend or CRM. Share this section with them.

1. Create a Customer Journey and add a Trigger-based entry.
2. Select the event that should start the Journey. Create a custom event in the Control Panel first if you haven’t already, for example RewardAvailable.
3. Add and configure a push element. Enable Send by User ID so the push reaches every device tied to the user, including the saved pass.
4. Finish configuring and activate the Journey.

When the entry event fires, Pushwoosh sends the push to every device tied to the user. Pass holders receive it as a lock-screen message on the pass. Users without an Apple Wallet pass receive it on their other devices.

Pass content

The push does not change any pass fields. To update pass content alongside the message, for example a points balance, update the pass separately via Edit in All passes or through the PassKit API.

Example: Notify a user that a reward is available

POST https://api.pushwoosh.com/json/1.3/postEvent

{
  "request": {
    "application": "XXXXX-XXXXX",
    "userId": "u12345",
    "event": "RewardAvailable",
    "attributes": {
      "reward": "Free coffee",
      "expires": "2026-07-01"
    }
  }
}

The event name must match an event created in your Control Panel.

Other ways to build the journey

The trigger-based flow above is one option. Depending on what should start the journey, choose a different entry element:

• Audience-based entry: start the journey for a whole segment instead of a single event. Run it once, on a schedule, or periodically (for example, every week to everyone holding an active pass), with new users entering as they join the segment.
• API-based entry: start the journey from a business event that happens outside the app, such as a flight delay or gate change. Your external system calls the entry element’s request template and passes a filter to target the right users, for example everyone who has a tag flightNumber = SU1234 set when the pass was issued. A good fit for boarding passes and event tickets.

Notify holders of a specific pass via API

To message everyone who saved one specific pass, call Update a pass. It updates the pass and notifies devices.

Update a pass