How does it all work?
[1] use the Passmeister website to setup your pass
[2] use the Passmeister API to create individual passes
[3] your customers download the passes to their Apple or Google Wallet app with the link (or QR-Code) you provide them
[4] you can update or delete the passes any time using the Passmeister API

(it really feels like magic, that Apple Wallet thing on my mother's iPhone will update instantly)

 What is a pass?
- Customer cards, membership cards, tickets, season passes, transport passes - anything that can be represented in Apple/Google Wallet.
- most passes show a barcode (QR-Code, Aztec, Code128, PDF147)

 What's so easy?
- you don't need to think about the completely different ways Apple and Google wallet passes are created and updated
- Passmeister creates the best designs for you to pick from (tell your boss it's AI, actually it's just algorithms)
- (designs are also fully customizable)
- you don't need a Mac (yes, even for your required Apple Certificates - you still need an Apple developer account, but that works in any browser)
- (YMMV, I still love my Macbook)
- Passmeister creates all necessary images assets, you just provide a logo and one image
(last time I counted there was a total of at least 11 different image files for an Apple and Google Wallet pass, are you kidding me?)
- you could even use different images for each created pass

 Passmeister API
- is a REST API, authenticated with an API token
- naming API fields is fully customized: if you want your passes to show the fields customerId, legacyOldId and coffeeKingStatus, you can have it.
- a complete OpenAPI specification with your individual pass fields is available as a JSON file.
(Works great in tools like Postman, VS Code or JetBrains IDEs.)
- we also provide Swagger UI for you to visualize and interact with your live API

basically you can use:
- POST /pass to create or update a pass
- GET /pass to retrieve data for a pass (like URLs/QR-Codes)
- GET /pass/list to list all your pass ids
- DELETE /pass (I'm curious what that one does)

You can use your own pass IDs, for example customer IDs from your database.
(This way, you don't even need to store anything returned by Passmeister API.)

 Languages & locales
- Passes can be created in any locale/language and support multiple locales/languages in a single pass
- the Passmeister API is available in English (mostly error messages, which will of course never happen)
- the Passmeister website (where you edit settings etc.) is available in English and German

 What else can it do?
- for distribution, you provide your users with a single link
(It's tricky behind the scenes, Apple uses self-contained wallet files, Google a JWT claim against their servers.)
- accessing that link can be protected with a PIN for a bit of security

- Passmeister API is not officially known by any acronym (but you may still call it PAPI)
- it's just the easiest API for the most beautiful passes