Translations exist for many types of data, such as stops, bicycle rental stations and parking areas. Some data sources\ndon't provide translations. It's possible that stops that originate from one source have translations for names, while\nsome others don't. If there are translations, typically the two available languages are Finnish (fi) and Swedish (sv).\nOccasionally, for example for parking areas, there are also English (en) translations.
Texts that can be translated are automatically translated in the GraphQL query responses if the standard Accept-Language header is used.\nSo for instance, if Accept-Language: sv header is sent in the GraphQL request, a query like { vehicleParkings { name } } would return\nthe parking names in Swedish, if available.
Typically, it's enough to fetch the fields in one language. However, sometimes one might want to display some field with multiple languages\nat once, for example. In that case, it's possible to fetch the same field multiple times and use a language parameter on the field to\nspecify the requested language (this overrides the language from the Accept-Language header). Here's an example on how to use this on\nvehicle parking:
{\n vehicleParkings {\n nameFi: name(language: \"fi\")\n nameSv: name(language: \"sv\")\n nameEn: name(language: \"en\")\n }\n}