WalletPlatform API
Create and manage digital wallet passes for Apple Wallet and Google Wallet through one consistent REST API.
🚀 Quick Start
Get your first pass live in under 5 minutes — token, create pass, redirect.
Get started →🔑 Authentication
OAuth2 client-credentials flow. JWTs are signed RS256, valid 60 minutes.
Authentication →📖 API Reference
Full reference of all customer endpoints (OpenAPI, rendered with Redoc).
Open API Reference →Base URL
https://api.walletplatform.io/api/v1
What you can build
- Loyalty cards with real-time point updates and member-id barcodes.
- Event tickets with QR codes and seat / row data.
- Boarding passes for air, train, bus or boat — transit-type aware.
- Coupons & offers with expiry handling and barcode payloads.
- Generic passes for any other use case that fits a header + barcode.
Core concepts
Tenants & Applications
Every API call is scoped to a tenant_id (your organisation) and an
application_id (one credential pair per integration). Secrets are
Argon2id-hashed at rest.
Templates
Templates define the look and feel of a pass (colors, fields, barcode behaviour). Authored in the Web UI; consumed read-only by this API. See Templates.
Passes
A pass is an instance of a template for one end-user. Issued asynchronously —
the API returns 202 Accepted and a job_id; poll
GET /passes/{id} until status is
active or partial.
Multi-provider routing
A pass can be issued to Apple Wallet and Google Wallet simultaneously. The
providers object on each pass response surfaces per-provider
state, save links and download URLs.