Apple Wallet Pass API
Let users add .pkpass passes (tickets, coupons, membership cards) from your web app to Apple Wallet.
The Apple Wallet Pass API lets your web app hand a .pkpass file (event ticket, boarding pass, coupon, loyalty or membership card) to the user so they can add it to Apple Wallet.
How to Use:
Link to your .pkpass file, but replace the https:// prefix of the file URL with addpkpass://:
<a href="addpkpass://example.com/passes/ticket.pkpass">Add ticket to Apple Wallet</a>
How It Works:
- The app converts the
addpkpass://link back to ahttps://URL. - The pass URL is opened in an in-app browser tab, which recognizes the
.pkpasscontent and shows the native Add to Apple Wallet preview. - The user confirms and the pass is stored in the Wallet app.
Notes: The pass must be served over HTTPS with the correct application/vnd.apple.pkpass MIME type, and it must be signed with a valid Apple Pass Type ID certificate (see the Apple Wallet Passes documentation for how to generate passes).
SDK-style implementation notes
Treat this feature as a native capability exposed to your web layer: keep your production website or PWA as the source of truth, then use the documented WebViewGold configuration flags, URL commands, and JavaScript bridge calls to opt in to native iOS behavior only where it adds value. This approach keeps your codebase maintainable because the same web application can serve browsers, WebViewGold for iOS, and the other WebViewGold platforms with minimal conditional logic.
For reliable results, prefer HTTPS endpoints, stable route names, explicit success/error states in your UI, and small JavaScript helper functions that wrap native calls. For example, a web app built with jQuery Mobile, Lovable, Base44, Bolt, WordPress, Bubble, a custom React/Vue/Angular stack, or static HTML can expose a single button or event handler that triggers the native WebViewGold API while still showing a graceful browser fallback.
- Recommended integration pattern: detect the app context, call the WebViewGold API, then update your web UI after the native callback or route change.
- Testing checklist: validate the feature on a real device or packaged build, verify permissions and store review text, and confirm that browser-only users still receive a useful fallback.
- SEO benefit: keep feature pages, route titles, and structured content indexable on your website while WebViewGold delivers the native app shell for iOS users.