触发推送通知
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
合作伙伴触发的通知
添加消息和通知
背景
用户添加卡券后,您可能需要向其发送与卡券相关的消息,并确保他们收到相关通知。使用 Add Message API 请求(message_type
等于 TEXT_AND_NOTIFY
)时,会发生以下情况:
- 系统会将“消息”项添加到“卡券背面”(也称为详细信息模板),并向保存了卡券的用户发送推送通知。
- 用户点按通知后,Google 钱包会打开到卡券正面(也称为卡片视图),并且用户会在屏幕顶部看到带有“查看消息”按钮的宣传信息。
- 点击宣传信息后,用户会进入卡券背面,其中会突出显示新的消息(未读)。
向用户发送包含通知的消息时的一些注意事项
- 用户必须为其卡券启用通知,才能接收与消息相关的推送通知。
- 消息可能包含指向您的网站或应用的 URI。超链接必须是与卡券相关的网站或应用。将用户引导至与卡券无关的链接违反了可接受的使用政策。
- 您在 24 小时内最多只能发送 3 条可触发推送通知的消息。如果 Google 认为您向用户发送的推送通知属于垃圾内容,可能会限制您的推送通知传送配额。
- 用户在锁定屏幕上看到的推送通知由 Google 钱包控制。
- 您可以使用 UPDATE 或 PATCH 方法,通过常规类或对象端点修改或移除消息数据。
集成步骤
如果您想使用 AddMessage API 向用户发送有关添加的新发卡人消息的通知,则需要更新 AddMessageRequest,以便包含新文本的 Message 的 MessageType 为 TEXT_AND_NOTIFY,而不是 TEXT。
在 Passes 类中添加消息和通知的 JSON 请求示例
…
"id": ISSUER_ID.CLASS_ID",
"message":
{
"header":"My Class message header",
"body": "My Class message body with a <a href="https://wallet.google">Hyperlink<\a>",
"id": "message_id",
"message_type": "TEXT_AND_NOTIFY"
},
…
在卡券对象中添加消息和通知的 JSON 请求示例
…
"id": OBJECT_ID",
"classId": "ISSUER_ID.CLASS_ID",
"message":
{
"header":"My Object message header",
"body": "My Object message body with a <a href="http://play.google.com/store/apps/details?id=com.google.android.apps.maps">Hyperlink<\a>",
"id": "message_id",
"message_type": "TEXT_AND_NOTIFY"
},
…
添加消息并为通过类发送通知的示例响应
// The updated resource
…
{
"kind": "walletobjects#walletObjectMessage",
"header": "My Object message header",
"body": "My Object message body with a <a href="http://play.google.com/store/apps/details?id=com.google.android.apps.maps">Hyperlink<\a>",
"id": "message_id",
"messageType": "textAndNotify"
},
…
异常处理
如果尝试发送通知的次数超过 3 次,系统会返回 QuotaExceededException 响应。如集成步骤中所述,您可以使用“TEXT”而非“TEXT_AND_NOTIFY”设置卡券的任何其他更新。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-08-29。
[null,null,["最后更新时间 (UTC):2025-08-29。"],[[["\u003cp\u003eSend messages to Google Wallet pass users and trigger a push notification using the \u003ccode\u003eTEXT_AND_NOTIFY\u003c/code\u003e message type with the Add Message API.\u003c/p\u003e\n"],["\u003cp\u003eUsers will see a callout on their saved pass prompting them to view the new message, leading them to the pass details.\u003c/p\u003e\n"],["\u003cp\u003eYou can send a maximum of 3 notification-triggering messages per pass within a 24-hour period, with potential throttling for excessive notifications.\u003c/p\u003e\n"],["\u003cp\u003eThe message content can include links to relevant websites or apps associated with the pass, adhering to Google's Acceptable Use Policy.\u003c/p\u003e\n"],["\u003cp\u003eMessages and notifications can be managed through the \u003ccode\u003eUPDATE\u003c/code\u003e or \u003ccode\u003ePATCH\u003c/code\u003e methods for editing or removal.\u003c/p\u003e\n"]]],["The `Add Message API` with `message_type` as `TEXT_AND_NOTIFY` adds a message to the pass's back and sends a push notification. Users tap the notification to view the pass and then access the message, highlighted as unread. Messages can include URIs relevant to the pass. A maximum of 3 notifications are allowed per 24 hours. Use the `AddMessageRequest` and set `MessageType` to `TEXT_AND_NOTIFY`. Exceeding the notification limit triggers a `QuotaExceededException`. `TEXT` can still be used.\n"],null,["# Trigger Push Notifications\n\nPartner Triggered Notifications\n-------------------------------\n\n### Add Message and Notify\n\n#### Background\n\nAfter a user adds a pass you may want to send them a message related to the\npass and ensure they are notified about it. Using the [Add Message API](/wallet/generic/rest/v1/genericclass/addmessage)\nrequest with a `message_type` equal to\n**`TEXT_AND_NOTIFY`** the following occurs:\n\n1. A \"[Message](https://developers.google.com/wallet/reference/rest/v1/Message)\" item is added to the \"back of pass\" (aka [Details\n Template](/wallet/generic/resources/template#details-template)) and a push notification is sent to users with the pass saved.\n2. Once the user taps the notification it opens Google Wallet to the front of the pass (a.k.a. Card view) and the user will see a callout at the top of the screen with a \"View Message\" button.\n3. Clicking the callout will take users to the back of the pass, where new unread messages are highlighted.\n\n#### Some considerations when sending messages with notifications to users\n\n- Users must have notifications enabled for their passes to receive the push notifications related to messages.\n- Messages may contain URIs to your website or app. Hyperlinks must be a website or app related to the pass. It is a violation of the [Acceptable Use Policy](https://payments.developers.google.com/terms/aup) to send users to links not related to the pass.\n- You may send a maximum of 3 messages that trigger a push notification in a 24 hour period. Google may throttle your push notification delivery quota if it deems you are spamming your users.\n- The push notification users see on their lock screen is controlled by Google Wallet.\n- You can use the [UPDATE](/wallet/generic/rest/v1/genericclass/update) or [PATCH](/wallet/generic/rest/v1/genericclass/patch) methods to edit or remove message data using the regular class or object endpoint.\n\n#### Integration Steps\n\nWhen you want to notify users about a new issuer message added using the\nAddMessage API, you will need to update the [AddMessageRequest](https://developers.google.com/wallet/reference/rest/v1/AddMessageRequest)\nso that the [Message](https://developers.google.com/wallet/reference/rest/v1/Message)\nwhich contains your new text has the [MessageType](https://developers.google.com/wallet/reference/rest/v1/Message#MessageType)\n**TEXT_AND_NOTIFY** instead of **TEXT**.\n\n#### Example JSON Request to add message and notify in a Passes Class\n\n```carbon\n ...\n \"id\": ISSUER_ID.CLASS_ID\",\n \"message\":\n {\n \"header\":\"My Class message header\",\n \"body\": \"My Class message body with a \u003ca href=\"https://wallet.google\"\u003eHyperlink\u003c\\a\u003e\",\n \"id\": \"message_id\",\n \"message_type\": \"TEXT_AND_NOTIFY\"\n },\n ...\n```\n\n#### Example JSON Request to add message and notify in a Passes Object\n\n```carbon\n ...\n \"id\": OBJECT_ID\",\n \"classId\": \"ISSUER_ID.CLASS_ID\",\n \"message\":\n {\n \"header\":\"My Object message header\",\n \"body\": \"My Object message body with a \u003ca href=\"http://play.google.com/store/apps/details?id=com.google.android.apps.maps\"\u003eHyperlink\u003c\\a\u003e\",\n \"id\": \"message_id\",\n \"message_type\": \"TEXT_AND_NOTIFY\"\n },\n ...\n```\n\n#### Example [Response](/wallet/generic/rest/v1/genericclass/addmessage#response-body) to add message and notify for a Pass Class\n\n```scilab\n // The updated resource\n …\n {\n \"kind\": \"walletobjects#walletObjectMessage\",\n \"header\": \"My Object message header\",\n \"body\": \"My Object message body with a \u003ca href=\"http://play.google.com/store/apps/details?id=com.google.android.apps.maps\"\u003eHyperlink\u003c\\a\u003e\",\n \"id\": \"message_id\",\n \"messageType\": \"textAndNotify\"\n },\n …\n```\n\n#### Exception handling\n\nAny attempts to notify more than 3 times will yield a\n**QuotaExceededException** response. Any further updates to the\npass can be set using \"**TEXT** \" instead of\n\"**TEXT_AND_NOTIFY** \" as discussed in the [Integration\nSteps](#add-message-and-notify-integration-steps)."]]