Send each member their own wallet pass through the API
Create one QR code per member with the CodeQR API, set what each wallet pass shows, build each member's add-to-wallet link and update the passes later.

If you have a list of members, customers or ticket holders, each of them can get their own wallet pass: one QR code per record, with the member's number printed under the code, and a link that adds the pass to Apple Wallet or Google Wallet. You create the codes through the API and send each person their link. To add a single code to a wallet from the dashboard, read Add a QR code to Apple Wallet and Google Wallet first. For API keys and automation tools, see QR codes through the API, MCP and automations.
What you need
- Plan: Business or above, outside a trial. On any other plan the API refuses a
walletPasswith403 forbidden, and no code is created. Plans are on the pricing page. - An API key from your workspace, sent as
Authorization: Bearer <key>tohttps://api.codeqr.io. - A dynamic QR code per member. The pass carries the code's short link, so you can change where it points after the pass is saved. A static code writes its content into the pass instead, and that content can't change. Read Dynamic vs static QR codes before you choose.
Create one code per member
POST /qrcodes takes a walletPass object next to the usual fields:
barcodeText: the line of text under the QR code on the pass, up to 40 characters. Use the member's name or number.name: replaces your workspace name at the top of the pass, up to 64 characters.logo: replaces your workspace logo. Send the URL of an image uploaded withPOST /qrcodes/logo, or an https URL that serves a PNG, JPEG or WebP image without a redirect. CodeQR copies an external image to its own storage and returns the URL of the copy.
All three are optional. Anything you leave out shows your workspace's name and logo.
curl -X POST https://api.codeqr.io/qrcodes \
-H "Authorization: Bearer $CODEQR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"domain": "go.example.com",
"type": "url",
"url": "https://example.com/members/0042",
"title": "Central Bakery membership",
"walletPass": { "name": "Central Bakery", "barcodeText": "Member 0042" }
}'The response is the full QR code. These are the fields you need from it (the rest is left out here):
{
"id": "qr_123",
"domain": "go.example.com",
"key": "Opf4TLRtxp8s-qr",
"shortLink": "https://go.example.com/Opf4TLRtxp8s-qr",
"walletPass": { "name": "Central Bakery", "barcodeText": "Member 0042" }
}Give the code a clear title. Without one, Apple Wallet shows the code's type and Google Wallet shows "QR Code" as the pass title.
For a long list, POST /qrcodes/bulk takes an array of up to 100 codes in one request, each with its own walletPass. The response is an array in the same order, and every entry carries its own walletPass:
[
{
"id": "qr_124",
"domain": "go.example.com",
"key": "42MlNp1OEmTV-qr",
"shortLink": "https://go.example.com/42MlNp1OEmTV-qr",
"walletPass": { "barcodeText": "Member 0043" }
},
{
"id": "qr_125",
"domain": "go.example.com",
"key": "C2dFxpj4YZhs-qr",
"shortLink": "https://go.example.com/C2dFxpj4YZhs-qr",
"walletPass": { "barcodeText": "Member 0044" }
}
]Store the id next to the member in your own system. You need it to update the code later.
Build each member's link
Take domain and key from the response and build:
https://<domain>/pass/<key>/add
For the first code above that is https://go.example.com/pass/Opf4TLRtxp8s-qr/add. The link decides by device: iPhone, iPad and Safari on a Mac go straight to Apple Wallet, Android goes straight to Google Wallet, and everything else lands on the code's pass page, where the person picks a wallet. In-app browsers such as Instagram's or LinkedIn's can't hand a pass to the wallet, so they get the pass page too. The wallet pass article covers the details, including /apple and /google for a fixed wallet.
Then send the link where the member will open it on their phone: the sign-up confirmation email, the order confirmation, or a button in your members' area. A link opened on a computer shows the pass page.
Change a pass later
Update a code with PUT /qrcodes/<id>. For walletPass, three rules apply:
- Leave
walletPassout and the stored value stays. - Send
nulland it is cleared. - Send an object and it replaces the stored one as a whole. Fields you leave out of the object are cleared, not merged.
Because of the third rule, this update, which sends only barcodeText, removes the name set at creation:
{ "walletPass": { "barcodeText": "Member 0042 (Gold)" } }The response then carries only that field:
"walletPass": { "barcodeText": "Member 0042 (Gold)" }To change one field, send the whole object again with that field changed.
What reaches a pass that someone already saved depends on what you change:
- The destination of a dynamic code: every saved pass opens the new one. No one has to save the pass again.
- Text, name and logo: a change reaches only passes saved after it. People who saved earlier keep the old version until they save the pass again.
- A static code: to change its content, create a new code and send that member the new link.
Archiving a code marks the passes saved in Google Wallet as expired.
Troubleshooting
The message says custom wallet pass branding requires a plan that includes it and can't be used during a trial. Your workspace is below Business or still in its trial. Nothing is created. Sending walletPass: null is always accepted.