[null,null,["最后更新时间 (UTC)：2025-08-29。"],[[["\u003cp\u003eThere are four ways to add links to Boarding Passes, including options for linking to all passes of a class or specific passes.\u003c/p\u003e\n"],["\u003cp\u003eApp linking allows you to guide users to your branded experiences, with links appearing at the bottom of the pass.\u003c/p\u003e\n"],["\u003cp\u003eYou can set the \u003ccode\u003eFlightObject.appLinkData\u003c/code\u003e field to the URI or package name of your app or website to enable app linking for a Boarding Pass.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eappLinkData\u003c/code\u003e field includes options for specifying Android app links, web app links, and display text, with a 30-character limit for display text.\u003c/p\u003e\n"],["\u003cp\u003eYou can alternatively use \u003ccode\u003etargetUri\u003c/code\u003e under \u003ccode\u003eandroidAppLinkInfo\u003c/code\u003e to link to the Play store listing for your app instead of deeplinking to the app directly.\u003c/p\u003e\n"]]],["Links can be added to Boarding Passes via `FlightClass.LinksModuleData` (for all passes) or `FlightObject.LinksModuleData` (for specific passes). App links, displayed at the bottom of the Pass, can be added through `FlightObject.appLinkData` (specific pass) or `FlightClass.appLinkData` (all passes). `appLinkData` allows navigation to an app or website, specifying the package name or URI. The display text is limited to 30 characters. Web links are enabled with `webAppLinkInfo` and `androidAppLinkInfo` can direct the user to the Play Store or to the app.\n"],null,["# Add links to your Boarding pass\n\nThere are four ways to add links to a Boarding Pass.\n\n- Use `FlightClass.LinksModuleData` to add links to all Boarding Passes that are associated with the `FlightClass`.\n- Use `FlightObject.LinksModuleData` to add a link to a specific Boarding Pass `FlightObject`.\n- Use [FlightObject.appLinkData](/wallet/tickets/boarding-passes/rest/v1/AppLinkData) to place an app link at the bottom of that particular Pass.\n- Use [FlightClass.appLinkData](/wallet/tickets/boarding-passes/rest/v1/AppLinkData) to place an app link at the bottom of all the passes of that class.\n\n\nOne benefit of *app linking* is that it empowers your call-to-action to navigate\nusers to your branded experiences from Google Wallet. Links with this feature appear at the bottom\nof the Pass.\n\n### Feature example\n\n|--------|\n| |\n| Issuer |\n\n### Set the app link on your Google Wallet pass\n\nFor a given Boarding Pass, set the field `FlightObject.appLinkData`\nto the URI or Package name of your app or website.\n\n\nSee the format and context of the `appLinkData` field in the following source code:\nThe `displayText` field is limited to 30 characters.\n**Note:** To deep link to a specific view within an app you must use webAppLinkInfo. \n\n```\n {\n \"id\": string,\n \"classId\": string,\n …\n …\n …\n \"appLinkData\": {\n \"androidAppLinkInfo\": {\n \"appTarget\": {\n \"packageName\": \"com.google.android.gm\",\n }\n },\n \"webAppLinkInfo\": {\n \"appTarget\": {\n \"targetUri\": {\n \"uri\": \"https://mail.google.com/mail/\",\n \"description\": \"Web link for Gmail\"\n }\n }\n }\n \"displayText\": {\n \"defaultValue\": {\n \"value\": \"Our awesome app!\"\n }\n }\n }\n }\n```\nFor posterity the following implementation will also work. \n\n```\n{\n \"id\": string,\n \"classId\": string,\n …\n …\n …\n \"appLinkData\": {\n \"androidAppLinkInfo\": {\n \"appTarget\": {\n \"targetUri\": {\n \"uri\": \"https://play.google.com/store/apps/details?id=com.google.android.gm\",\n \"description\": \"Play store link for Gmail app\"\n }\n }\n }\n }\n}\n```"]]
