Skip to main content
Issuing a pass doesn’t put it on a phone. You send the holder a link, and they add the pass from a page hosted by TapAce. The page shows Add to Apple Wallet, Add to Google Wallet or both, depending on the pass’s platforms:
  • iPhone: the Apple Wallet sheet opens on its own, with the buttons as a fallback.
  • Android: the page goes straight to Google Wallet’s save screen.
  • Computer: the page shows a QR code to scan with a phone.
There are two kinds of link. Every pass has a distributionUrl:
The link never changes, so you can store it and send it at any time, for example in a welcome email or a text message. Anyone with the link can add the pass, so share it only with the holder. After you void the pass, the page says it’s no longer available.

​
Your own buttons

To put wallet buttons in your own app or email instead of linking to the page, use the pass’s direct links:
  • appleDownloadUrl downloads the signed Apple Wallet file.
  • googleSaveUrl opens Google Wallet’s save screen.
Each is null when the pass wasn’t issued for that wallet, can’t be signed right now, or is voided. Use the official Add to Apple Wallet and Add to Google Wallet buttons. For a link that stops working after a set time, create a download link:
The url is returned only once, so send it straight away. You can revoke a link before it expires. Once the pass is in a wallet it stays there after the link expires.

​
After the pass is added

​
Use the Node.js SDK

tapace.passes.create() returns the pass ID, distributionUrl and nullable wallet-specific links. Save the pass ID and share the distribution URL through your own application. Issuance does not install the pass automatically. See the SDK quickstart. Expiring download-link creation and revocation use the HTTP API; SDK 0.1.0 has no dedicated methods for them.