Emitir el pase de Google Wallet
Wallet passes
POST /v1/loyalty/memberships/{id}/passes/google
Issue the Google Wallet pass for a membership and get the save link to send to the customer.
POST
Emitir el pase de Google Wallet
Issues the Google Wallet card for a membership and returns the save link — the URL that opens Google Wallet with the card ready to add. Send it by WhatsApp, put it behind a button, or turn it into a QR code.
Endpoint
Required scope
loyalty:write
Headers
Path parameters
No body.
Example request
Response
201 Created
400 Bad Request
The program has no published wallet template — see the notes.401 Unauthorized
Missing, invalid, revoked, or expired token.403 Forbidden
The token does not have theloyalty:write scope.
404 Not Found
No membership with that id in your company.502 Bad Gateway
The loyalty service is unreachable, or Google Wallet rejected the request.Operational notes
- A published wallet template is required. Without one the call fails with
400 no published wallet template for this program. Design and publish the card in the Keebai portal first, then check withGET /v1/loyalty/templatesthat a version haspublished: true. - Calling twice is safe. The second call reuses the existing pass instead of creating a duplicate, and returns the same
provider_ref. Reissue freely if the customer lost the link. - The save link does not expire on our side, but it is a signed Google artefact — treat it as single-customer and do not publish it anywhere shared. Anyone with the link can add that specific card.
- The card is live after it is added. Later ledger movements push the new balance to it automatically; you do not reissue to update a number.
provider_refis the Google Wallet object id, useful if you also work against Google’s API directly. It is not needed for anything in this API.
Authorizations
Personal Access Token con prefijo kbai_pk_. Generar desde el portal con permiso developer.manage_tokens.