Response language
The API responds in English by default, or in French. The language applies to error messages and to content generated by eldo wallet.
The language is read in this order:
- the
?lang=enquery parameter - the
x-lang: enheader - the
Accept-Languageheader
- curl
- SDK Node.js
- nodejs
- php
- python
- java
- csharp
- go
- ruby
- CURL
curl -L 'https://api-v2.test.eldowallet.fr/clients/unknown?lang=en' \
-H 'Accept: application/json' \
-H 'x-lang: en' \
-H 'Authorization: Bearer <token>'
{"message": "Model not found!", "errorCode": "404:MODEL_NOT_FOUND", "path": "/clients/unknown?lang=en", "date": "…"}
note
A few validation messages are always in English, even when you request French (for example departureDate must be a valid ISO date). Always test errorCode, never message.
Your pass content
The API language doesn't translate your passes: the text you send (details, terms, event name…) is displayed as is. For a multilingual audience, create one template per language, or adapt the pass fields for each customer.