Apple Wallet and Google Wallet API guides
The eldo wallet API creates Apple Wallet and Google Wallet passes and keeps them up to date. The most common case: your loyalty card, designed once then sent to each of your customers, with up-to-date points. The same logic applies to coupons, event tickets, transit tickets and hotel bookings: you design a template once, then issue one pass per customer.
QuickstartYour first loyalty card in 10 minutes.
API referenceEvery endpoint, with its parameters, responses and errors.
Use casesEnd-to-end flows by industry, step by step.
Knowledge baseConcepts, FAQ and troubleshooting.
At a glance
| Base URL | https://api-v2.test.eldowallet.fr (test, default) — environments |
| Authentication | Authorization: Bearer <token> — details |
| Format | JSON; multipart/form-data for endpoints that accept images — details |
| Response language | x-lang: fr or en — details |
| Errors | A single envelope {message, errorCode, path, date} — list of codes |
| Pagination | ?page=1&limit=10 — details |
| Rate limit | 1,000 requests per minute |
| OpenAPI specification | openapi.en.yaml · openapi.fr.yaml |
API objects
- Wallet: your eldo wallet workspace. It holds your branding, your sending settings and your access tokens.
- Template: the design and rules of a pass type (colors, image, barcode, security). Example: the "Café Lumière" loyalty card, or a "Marseille – Ajaccio crossing" ticket template.
- Pass: the copy issued to one person, with their data (name, seat, date…). It installs on the phone and updates remotely.
- Customer: a holder of the wallet's store card.
API v1
API v1 (api.eldowallet.fr/api/v1) will no longer be supported after December 31, 2026. See the migration guide.