Language Support

Livescore API's football data supports translations of team names in several different languages. In this page you can read more about this service.


Introduction


Due to the high interest in our football data, we have started supporting several major languages for some of our major API endpoints. To make it easy for you all you need to do is add another parameter to your already working livescore API integrated software, without the need of making any other changes. Right now 4 livescore api endpoints support translations of teams names in different langauges. These are: livescores, fixtures, historical matches, league standings.

If you notice any missing translations, do not hesitate to add them yourself though our volunteer as translator functionality in your profile. You need to be logged in.
If you need our football data in another language, that we do not support yet, please let us know trough our contact information.

Languages


As it is right now, we support English, Arabic, Farsi, and Russian as translations for the names of the teams. In order to apply the translation in your code you need to add the lang parameter to the URL that you are already using. The language codes that we use in our football data service are specified by ISO standard nomenclature: ISO 639-1. You can read more about this standard here (opens in a new tab). In the table below, we have listed the changes that you should do if you want to receive the names of the football teams in our services in the corresponding language. Examples with each language are shown under the table in the next section.
LanguageISO 639-1 CodeURL Addition
EnglishenNo change, it is our default data language
Arabicar&lang=ar
Farsifa&lang=fa
Russianru&lang=ru


Examples of changes


Here are the changes that you need to perform in order to take advantage of the team names translations. The example, here is shown on only one API endpoint, but it is performed in the same way for all of the livescore API endpoints that support translations.
Football data translation to Arabic
In this first example, we use the currently played matches api endpoint, and there are no filters on the scores . If you have any filters added like for example the league id, you still just add the &lang=ar in the end of the URL.

Before: http://livescore-api.com/api-client/scores/live.json?key=demo_key&secret=demo_secret
After: http://livescore-api.com/api-client/scores/live.json?key=demo_key&secret=demo_secret&lang=ar

Here is how the output of this this URL might look like. Although, the team names in the json keys home_name and away_name appear to be some scrambled letters and numbers, they are in fact valid UTF-8 encoded strings. Once displayed on your website, web app, or mobile app pages and views they will be correct.
{
    "success": true,
    "data": {
        "match": [
            {
                "id": "119771",
                "home_name": "\u0623\u0631\u0643\u0627 \u063a\u062f\u064a\u0646\u064a\u0627",
                "away_name": "\u064a\u0627\u063a\u064a\u064a\u0644\u0648\u0646\u064a\u0627 \u0628\u064a\u0627…",
                "score": "0 - 2",
                "ht_score": "0 - 0",
                "ft_score": "0 - 2",
                "et_score": "",
                "time": "FT",
                "league_id": "122",
                "status": "FINISHED",
                "added": "2018-12-04 19:26:01",
                "last_changed": "2018-12-04 21:27:11",
                "home_id": "898",
                "away_id": "445",
                "league_name": "Cup"
            }
            {
                "id": "119768",
                "home_name": "\u0631\u0627\u064a\u0648 \u0641\u0627\u064a\u064a\u0643\u0627\u0646\u0648",
                "away_name": "\u0644\u064a\u062c\u0627\u0646\u064a\u0633",
                "score": "0 - 1",
                "ht_score": "0 - 1",
                "ft_score": "0 - 1",
                "et_score": "",
                "time": "FT",
                "league_id": "203",
                "status": "FINISHED",
                "added": "2018-12-04 19:26:01",
                "last_changed": "2018-12-04 21:24:02",
                "home_id": "792",
                "away_id": "25",
                "league_name": "Copa del Rey"
            }
        ]
    }
}
Football data translation to Farsi
In this second example, we use the scheduled games api endpoint (e.g. fixtures), and here we have also applied the league filter so we only get the fixtures for the English Premier League. Once again the only thing that needs to be done is to add the string &lang=fa in the end of the URL.

Before: http://livescore-api.com/api-client/fixtures/matches.json?key=demo_key&secret=demo_secret&league=25
After: http://livescore-api.com/api-client/fixtures/matches.json?key=demo_key&secret=demo_secret&league=25&lang=fa
Football data translation to Russian
In this third example, we use the history data api endpoint, and here we have also applied the league filter so we only get the fixtures for the English Premier League. Once again the only thing that needs to be done is to add the string &lang=ru in the end of the URL.

Before: http://livescore-api.com/api-client/scores/history.json?key=demo_key&secret=demo_secret&league=25
After: http://livescore-api.com/api-client/scores/history.json?key=demo_key&secret=demo_secret&league=25&lang=ru