Choose the language of names, descriptions and traveller-facing messages.
Accepted headers
The recommended header is LANG:
http
LANG: es-ESThe standard HTTP header is also accepted:
http
Accept-Language: es-CO,es;q=0.9,en;q=0.8A language field in the body or query is still accepted for backwards compatibility, but prefer the headers.
Precedence
text
LANG > Accept-Language > body/query.language > en-USWith a composite Accept-Language, the first supported language wins. With no language at all, en-US is used.
Supported languages
| Language | Normalized value | Accepted aliases |
|---|---|---|
| English | en-US | en, en-US, english |
| Spanish | es-ES | es, es-ES, spanish, regional variants such as es-CO |
| German | de-DE | de, de-DE, german |
| French | fr-FR | fr, fr-FR, french |
| Portuguese | pt-BR | pt, pt-BR, portuguese |
| Chinese | zh-CN | zh, zh-CN, chinese |
| Italian | it-IT | it, it-IT, italian |
Unsupported language
json
{
"statusCode": 400,
"code": "transfer_invalid_language",
"message": "Unsupported transfer language: ru-RU"
}What gets localized
Amenity names and descriptions, vehicle and provider labels, goodToKnowInfo, pickupInstructions and flight verification messages all follow the requested language. Identifiers, tokens, currency codes and status values never change.
On a stream connection, the language is fixed when the connection opens and reused for every later event.