Now supporting Apple Wallet & Google Wallet

Wallet passes
built for developers

Issue, update and push Apple Wallet and Google Wallet passes to millions of users with a single REST API. No certificate complexity. No boilerplate.

Start for free Read the docs

javascript

import WalletPassAPI from '@walletpassapi/node';

const client = new WalletPassAPI({
  apiKey: process.env.WALLETPASS_API_KEY,
});

// Create a loyalty card in one API call
const pass = await client.passes.apple.create({
  organization_name: 'Coffee Rewards',
  pass_style:        'storeCard',
  background_color:  '#1a3d2b',
  primary_fields: [{
    key: 'points', label: 'Points', value: '250',
  }],
  barcode_message: 'MEMBER001',
});

// Send this URL to your user — opens directly in Apple Wallet
console.log(pass.download_url);

→ https://api.walletpassapi.com/pass/apple/e85ef879… 200 OK · 340ms

Why WalletPassAPI

Everything you need.
Nothing you don't.

We handle the certificate signing, APNs push connections, and Google Pay JWT generation so you can focus on building your product.

Simple REST API

One endpoint to create a pass. One to update it. One to push it. No SDKs required — curl works on day one.

Instant push updates

Update a pass field and push the change to every installed device in real time. No user action required.

All five pass types

Store cards, coupons, event tickets, boarding passes and generic passes — Apple Wallet spec fully covered.

Multi-tenant reseller API

Issue credentials to sub-accounts and allocate pass quotas. Build your own white-label wallet pass platform on top of ours.

Batch updates

Update thousands of passes in a single request by tag, template or serial number. Perfect for time-sensitive promotions.

Webhooks

Receive real-time events when passes are installed, removed or scanned. Connect to Zapier, your CRM, or your own endpoint.

Platform coverage

One API.
Both wallets.

Write your pass once. WalletPassAPI handles the platform differences — certificate signing for Apple, JWT signing for Google.

Apple Wallet Production

Full pass.json signing with your P12 certificate and WWDR chain. APNs push notifications delivered directly to iOS devices. All five pass styles supported.

Pass signing APNs push 5 pass types Barcode & NFC

Google Wallet Production

JWT-signed passes issued through your Google Pay Issuer account. Service account credentials managed securely server-side. Supports loyalty, generic, event and offer classes.

JWT signing FCM push 4 pass classes Issuer API

Getting started

Up and running
in minutes.

From zero to issuing live wallet passes in three steps. No Apple developer portal gymnastics on day one.

Create an account

Sign up and get your API key. Use it immediately against our sandbox to create test passes — no credentials required to start.

Add your credentials

Follow our interactive credential guide to register your Apple Pass Type ID and Google Issuer ID. We walk you through every step.

Issue passes

Call POST /api/v1/pass/apple with your pass data. Get back a URL. Send it to your user. Done.

Pricing

Simple, usage-based pricing.

Start free. Scale as you grow. No surprise bills.

Free

^$0

forever · no credit card

25 active passes
Apple Wallet
All pass types
REST API access
Pass Designer
Google Wallet
Push updates
Webhooks

Get started free

Common questions

Yes — to issue live passes to real devices you need an Apple Developer account ($99/year) to create a Pass Type ID and signing certificate. Our interactive credential guide walks you through the whole process in under 30 minutes. In the sandbox you can create and preview passes without any Apple account at all.

An active pass is one that has been created and is stored in our system. Deleting a pass frees up the slot. On paid plans, the pass limit is the number of new passes you can create per calendar month — rolling over unused is not supported, but updates and push notifications to existing passes are always unlimited and free.

As a reseller you get a pool of passes to distribute. You create sub-accounts for your customers, allocate a pass limit to each, and provide them with their own API keys. Your customers use the API exactly as a direct account would — they never know it's powered by WalletPassAPI. You set your own pricing and margin.

All Apple P12 certificates, private keys, and Google service account credentials are encrypted at rest using AES-256-GCM before storage. Credentials are decrypted only in memory at request time and are never logged or transmitted externally.

Yes, you can upgrade or downgrade at any time. Upgrades take effect immediately. If you downgrade and your existing pass count exceeds the new plan limit, you won't be able to create new passes until you're back within the limit — existing passes remain active.

Wallet passesbuilt for developers

Everything you need.Nothing you don't.