pkpassBuilder

Creating Apple Wallet passes for an event is more annoying than it should be. You need an Apple Developer account, a Pass Type ID certificate plus Apple's WWDR intermediate certificate, and then the real headache: hand-building the exact JSON structure that makes every field render the way you want in Wallet.

pkpassBuilder takes a JSON attendee list and turns it into a folder of ready-to-distribute .pkpass files — one per person, each signed, each with its own QR code and personalised fields like name, role and accreditation code. The QR can be built from any field in the JSON, so it encodes an email, an accreditation ID, or a custom token depending on how your check-in works. Branding, colours and layout come from a single config file, and images are auto-resized to Apple's spec so nothing shows up pixelated.

Where it really earns its keep is the details most ticketing platforms get wrong. Passes expire the moment the event ends — no clutter left behind, unlike services such as Weezevent or promoters like Ataquilla that let passes linger in Wallet for months, sometimes over a year. Passes that share a Pass Type Identifier group together under one event instead of scattering among unrelated ones. And it wires up relevant-location and relevant-date fields, so the pass surfaces on the lockscreen exactly when and where the attendee needs it.