Put every guest's ticket in their phone before doors, and when the venue or the start time changes, push one update that reaches every ticket at once, with no app for guests to install.
A whole season of events runs on $39 a month.
The self-serve alternative to PassKit, PassNinja, or PassEntry, with public pricing.
If the door needs to check it, the ticket can carry it, from seats and gates to tables and doors-open times.
Tap any card to test it live on your phone.
Set your brand color, logo, fields, and barcode in the visual editor, with a live preview and no code. The field reference has the full list.
Each guest's ticket is one POST /api/passes. Issue them whichever way fits:
Loop a script over your exported guest list, one POST per guest. See the create call.
Add guests by hand in the Pass Manager. Right for a dinner, a launch party, or a will-call list.
Connect your checkout or RSVP form through Zapier, n8n, or a plain HTTP request, and every sale becomes a ticket automatically.
Every ticket gets a branded link that opens the right wallet for whoever taps it. Email or text it once; it stays the same through every change you push.
Put the ticket ID in the barcode and pick the format your scanner already reads: QR, PDF417, Aztec, or Code128. We render the barcode; your check-in app decides what a valid scan means.
Issue, change, upgrade, refund, and follow up, each one update to the ticket the guest already holds, from the Pass Manager or your own system.
Issue an entire guest list in one batch, with one install link per person and every ticket carrying the details they need.
A ticket reaches the guest's wallet
When the venue changes, update every ticket already issued and notify every guest's lock screen at once.
The new venue, on every lock screen
Move a guest to VIP on the ticket already in their wallet, adding the new entry details without issuing a replacement.
The same ticket, now VIP
When a ticket is refunded, revoke it so it greys out, loses its barcode, and releases the seat for resale.
A refunded ticket, greyed out everywhere
Keep the ticket useful after the event with one update that rolls it forward to the next date, so the new invitation is already installed.
The ticket rolls forward to the next date
The API is plain HTTP, so anything that can export a list or fire a webhook can issue and update tickets.
Pull your guest list out of the Pass Manager as a CSV. Each row carries the ticket's share URL, ready for a mail merge.
Eventbrite exports, Luma lists, and plain spreadsheets all work the same way: one HTTP call per guest, direct or through Zapier or n8n, with no plugin to keep updated.
Billing counts each ticket you issue and each update that changes it. One ticket covers both wallets and counts once, and a revoke is free. PassKit runs around $1,300/month for the same lifecycle.
Under 1% of the included 100,000, about 10 cents a guest, with the venue change pushed to all 400 phones.
A tenth of the included 100,000. Even a 250,000-pass festival month is $39 + 150,000 x $0.00039 = $97.50.
One pass covers both Apple and Google and counts once. Creations and content updates count, revokes do not. Full pricing.
No. Apple Wallet and Google Wallet are built into every iPhone and Android phone. A guest taps Add to Wallet on the ticket's page, or on the .pkpass you email them, and the ticket is in their wallet.
Yes. Design the ticket in the visual editor, then run the event from the Pass Manager: add a guest, push a change, resend a link, or revoke a refund, all by clicking. The API is optional.
You PUT the ticket's serial with the new details and every installed copy updates in place, same link, same barcode, no reissue. Set a changeMessage on the changed field and it becomes the lock-screen banner on Apple ("Doors now 8:00 PM"); Google shows its own banner and your text appears inside the ticket.
Every ticket carries your ticket ID in barcodeValue, rendered as QR, PDF417, Aztec, or Code128. Scan it with any reader or check-in app and validate the ID against your guest list. We render the barcode; you decide what a valid scan means.
Yes. One POST /api/passes returns the signed Apple .pkpass and a Save to Google Wallet link for the same ticket, and it counts as one pass. Updates, pushes, and revokes work on both.
The ticket lives on our servers, so nothing is lost. Resend the same install link and the current ticket, with the latest venue and time, adds to the replacement phone under the same ticket ID.
Your choice. Tickets ship with the Apple Wallet share button hidden (sharingProhibited), which locks the live pass to the guest who added it; set it to false and the ticket is transferable. A screenshot is always possible, but the barcode resolves to one ticket ID, so a copied image reads as the same ticket twice at the door.
Revoke it with one call, or one click in the Pass Manager, and the ticket greys out, drops its barcode, and moves to expired passes on both wallets. Revokes are free and do not count against your quota.
It renders as a clean branded Wallet card on the generic and storeCard layouts, the same shape you see on this page, rather than Apple's event-ticket template. The barcode, guest details, and live updates behave the same in both wallets.
Yes. The ticket doubles as the badge. PUT the day's room or agenda each morning with a changeMessage and every attendee's pass updates before the first session.
Issue the plus-one its own ticket with its own serial and barcodeValue, so the door can tell the two apart, and set sharingProhibited to false on it if the primary guest should forward it.
Pro is $39 a month flat with 100,000 passes a month included (creations plus updates), then $0.00039 per pass beyond that. A 400-guest party with a venue-change push to everyone uses 800 of the 100,000; a 5,000-badge conference with a schedule update uses 10,000. One ticket covers both wallets and counts once, and revokes are free.
Build a ticket and install it on your own phone tonight. Every new account starts with 30 days of Pro.
curl -X POST https://api.walletwallet.dev/api/passes …
