Skip to main content

Migrating from API v1

End of support for API v1: December 31, 2026

API v1 (https://api.eldowallet.fr/api/v1) will no longer be supported after December 31, 2026. New features are only available in v2.

Our support team will help you migrate: contact us to plan your move to v2.

Who is affected?​

Any integration that calls a URL starting with https://api.eldowallet.fr/api/v1/. If you only use the eldo wallet back office, you have nothing to do.

What changes​

v1v2
Base URLhttps://api.eldowallet.fr/api/v1https://api-v2.eldowallet.fr (production); to try it: https://api-v2.test.eldowallet.fr — environments
Wallet IDin the URL (/wallets/{wallet}/transits)derived from the token (/transits)
LoginPOST /users/loginPOST/auth/login
Server tokens—revocable wallet tokens
Error format{statusCode, status, messageCode, message}{message, errorCode, path, date} — details
Paginationvaries by endpointuniform ?page=&limit= — details
Bulk sending—up to 5,000 items, with progress tracking — details
Webhooksplain URLtyped events, retries — details

Main endpoint mapping​

Needv1v2
Create a transit templatePOST /wallets/{wallet}/transitsPOST/transits
Send a transit ticketPOST /wallets/{wallet}/transits/{transit}/sendPOST/transits/{transitId}/passes
Update a tripPATCH /wallets/{wallet}/transits/{transit}/trip/{tripNumber}PATCH/transits/{transitId}/passes/trip/{tripNumber}
Notify a tripPOST /wallets/{wallet}/transits/{transit}/trip/{tripNumber}POST/transits/{transitId}/passes/trip/{tripNumber}/notify
Create a couponPOST /wallets/{wallet}/couponsPOST/coupons
Send a couponPOST /wallets/{wallet}/coupons/{coupon}/sendPOST/coupons/{id}/passes/send
Create an eventPOST /wallets/{wallet}/eventsPOST/events
Create a customerPOST /customersPOST/clients
Redeem a passPUT /wallets/{wallet}/redeemPOST/passes/template/{templateId}/redeem/{barcode}
Create a hotel passPOST /wallets/{wallet}/hotelsPOST/hotels

In v2, boarding passes are issued as transit passes (type: "Air", see Airlines) and movie tickets as events (see Cinema).

Migration steps​

  1. Create a v2 wallet tokenYour server

    Log in to v2 and create a wallet token dedicated to your integration.

  2. Retrieve your templates in v2Your server

    List your templates in v2 to get their IDs, and create the ones your integration needs.

  3. Update your callsYour server

    Change the base URL, remove the wallet ID from paths, and adapt request bodies following the API reference.

  4. Update your error handlingYour server

    Test errorCode (e.g. 400:VALIDATION_ERROR) instead of statusCode / messageCode.

  5. Switch over and monitorYour server

    Switch over gradually, monitor errors, then turn off v1 calls before December 31, 2026.

The legacy v1 documentation remains available at api.eldowallet.fr/api-docs until the end of support.

API news, once a month

New endpoints, upcoming changes, guides and use cases. No spam, one-click unsubscribe.

Report a technical problem

An API error, a pass that does not update, an email that does not arrive? Describe the problem: our technical team will answer.

For a fast answer, include:

  • The method and endpoint (e.g. POST /clients)
  • The error code returned (errorCode) and the body sent
  • The date and time of the call
  • The identifiers involved (customer, template, pass)

Never include an API token or a password.

AI assistant

Beta

Loading…

AI-generated answers (Claude): double-check important details.

Sign in to use the assistant