Languages¶
Localized text is keyed by language code: the name maps returned by the feed and by the sport APIs (Name, names, market and outcome names) contain the codes that were requested. A code with no translation for an entity yields an empty name, so request only the languages you need.
Language codes¶
| Code | Language |
|---|---|
ar | Arabic |
az | Azerbaijani |
bg | Bulgarian |
bn | Bengali |
de | German |
el | Greek |
en | English |
es | Spanish |
fa | Persian |
fi | Finnish |
fr | French |
he | Hebrew |
hi | Hindi |
hr | Croatian |
hu | Hungarian |
id | Indonesian |
it | Italian |
ja | Japanese |
ka | Georgian |
kk | Kazakh |
ko | Korean |
ms | Malay |
nb | Norwegian (Bokmål) |
nl | Dutch |
pt | Portuguese |
ro | Romanian |
ru | Russian |
sl | Slovenian |
sr | Serbian |
th | Thai |
tk | Turkmen |
tl | Tagalog |
tr | Turkish |
uk | Ukrainian |
uz | Uzbek |
vi | Vietnamese |
zh | Chinese |
Two more codes behave differently from the rest:
en_Mob— English with shortened names: market, period and outcome names come back as1/2whereenreturnsWinner. Sport, category, tournament, event and competitor names are not available for this code.kg— accepted, but it is not an ISO 639-1 code (kyis Kyrgyz). Check which language it maps to before using it.
Translation coverage is data, not contract: a language can be fully translated for one entity type and absent for another, and the set grows over time. Check the languages your integration needs against a real response, and ask your account manager if a language you need is missing.