Multi-language content
The Turneo API returns content in English by default, but also supports other languages so API clients can retrieve (and, in some cases, upload) content in the language their guests expect. Multi-language responses are available on:
/v2/experiences/v2/options/v2/booking-orders/v2/bookings
To request content in a specific language, pass a language query parameter on GET requests, using one of the codes below:
| Language | Code |
|---|---|
| English | en |
| German | de |
| Spanish | es |
| French | fr |
| Italian | it |
| Croatian | hr |
| Slovenian | sl |
| Portuguese | pt |
curl -X GET "https://api.turneo.co/v2/experiences?language=de" \
-H "Accept: application/json" \
-H "X-API-Key: <your-api-key>"
Points to keep in mind when working with multi-language content:
- Not every experience has content translated into every language. Where a resource's serialized form includes a
localizedfield, you can check it to see which languages are available for that resource. - English is the fallback language: if you request a language that isn't available for a given resource, you get the English content back instead.
- Not every field is translated. Free-text fields (e.g.
description,highlight) are translated; status fields (status) and specific names (e.g.city,organizer.name) are not. - Pass
showTranslations=trueinstead of (or alongside)languageto get the full per-language object for a multilingual field — e.g.{"en": "Sunset Kayak Tour", "de": "Kajaktour bei Sonnenuntergang"}— rather than a single resolved string. This is useful if you want to cache all translations at once instead of making one request per language.