Send a notification to a pass
Sends (or schedules) a message to the wallet passes installed for this pass: Apple Wallet shows a lock-screen banner and stores the message in a back field; Google Wallet shows a push notification and stores it in the pass messages. By default the notification targets both platforms; set platforms to deliver to a single one (the other reports SKIPPED). Delivery is asynchronous: the notification is returned in PENDING (or SCHEDULED) status; poll it to observe per-platform progress. The pass must be ISSUED. Set sendAt to a future time to schedule; reuse an idempotencyKey to make retries safe (returns the existing notification with 200). Notifications targeting Google are limited to 3 per pass per 24 hours (429 with a Retry-After header beyond that); Apple-only notifications are not rate limited.
Requires the pass-notifications:write scope on the access token.
Authorizations
Passlet access token (plt_*) sent as Authorization: Bearer <token> or X-API-Key. Authorized scopes are listed per operation under x-required-scopes.
Path Parameters
Pass identifier
^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$Body
Message text shown on the pass and in the push notification
1 - 1000Wallet platforms to deliver to; omit to deliver to all platforms
1Wallet platform a notification is delivered to
apple, google Schedule delivery for a future time; omit to send immediately
^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$Unique per workspace. Reusing a key returns the existing notification (200) instead of sending a duplicate
8 - 100Provider-specific delivery options
Response
OK
Pass notification identifier
^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$Pass identifier
^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$Message text
Provider-specific options supplied at creation
Scheduled delivery time; null for immediate sends
^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$Overall delivery status: SCHEDULED (sendAt in the future, nothing dispatched), PENDING (delivery in progress), SENT (delivered on every applicable platform), PARTIAL (one platform sent, the other failed), FAILED (failed on every applicable platform), SKIPPED (no targeted platform was applicable)
SCHEDULED, PENDING, SENT, PARTIAL, FAILED, SKIPPED "SCHEDULED"
ISO 8601 timestamp
^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$ISO 8601 timestamp
^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$