Repository navigation
Missing new languages recently incorporated to the API: CA, GL, EU #72
Description
Describe the bug
Some days ago, Deepl announced new languages available: CA - Catalan, GL- Galician, EU - Basque, they are officially listed in the Deepl API Documentation:
https://developers.deepl.com/docs/getting-started/supported-languages
But if we make a call to getSourceLanguage, we get the following list:
[
{
name: "Arabic",
code: "ar",
},
{
name: "Bulgarian",
code: "bg",
},
{
name: "Czech",
code: "cs",
},
{
name: "Danish",
code: "da",
},
{
name: "German",
code: "de",
},
{
name: "Greek",
code: "el",
},
{
name: "English",
code: "en",
},
{
name: "Spanish",
code: "es",
},
{
name: "Estonian",
code: "et",
},
{
name: "Finnish",
code: "fi",
},
{
name: "French",
code: "fr",
},
{
name: "Hebrew",
code: "he",
},
{
name: "Hungarian",
code: "hu",
},
{
name: "Indonesian",
code: "id",
},
{
name: "Italian",
code: "it",
},
{
name: "Japanese",
code: "ja",
},
{
name: "Korean",
code: "ko",
},
{
name: "Lithuanian",
code: "lt",
},
{
name: "Latvian",
code: "lv",
},
{
name: "Norwegian",
code: "nb",
},
{
name: "Dutch",
code: "nl",
},
{
name: "Polish",
code: "pl",
},
{
name: "Portuguese",
code: "pt",
},
{
name: "Romanian",
code: "ro",
},
{
name: "Russian",
code: "ru",
},
{
name: "Slovak",
code: "sk",
},
{
name: "Slovenian",
code: "sl",
},
{
name: "Swedish",
code: "sv",
},
{
name: "Thai",
code: "th",
},
{
name: "Turkish",
code: "tr",
},
{
name: "Ukrainian",
code: "uk",
},
{
name: "Vietnamese",
code: "vi",
},
{
name: "Chinese",
code: "zh",
},
]To Reproduce
Steps to reproduce the behavior:
- Create a blank vanilla nodejs project.
- Install deepl library
- Setup the api token
- Create a main file and invoke
deepClient.getSourceLanguages()
Expected behavior
The new available languages should be listed: CA,GL, EU
Reacted by JanEbbing
Activity
JanEbbing commentedon Nov 11, 2025
We do not list them in the languages endpoint yet because they are in Beta and can only be used with the opt-in flag. Does this work for you? I think we need a redesign of the entire endpoint in order to facilitate things like this without forcing users to hardcode languages in their implementation, which will change over time.
brauliodiez commentedon Nov 11, 2025
Thanks for the feedback, we are trying the following:
We have tried as well:
But we got
"Bad request, message: "Value for 'target_lang' not supported"
what are we doing wrong?
Thanks
brauliodiez commentedon Nov 11, 2025
Ok, just realized,
enable_beta_languages: "1"It should be an string with the value "1".
Thanks