Lingvanex Translate provides a simple API for translating plain text and HTML between any of 100+ supported languages. No limits on requests or document length!
Also we offer a self-hosted translation solution to translate unlimited volumes for a fixed price. So for just $50 you can translate millions of web-pages, audio and files per day.
To get free trial write us to [email protected]
Postman Collection: https://www.postman.com/lingvanex-api/lingvanex-api/collection/euq6pul/lingvanex-api
Translation Quality: https://lingvanex.com/translate/
Support Email: [email protected]
Developer: https://lingvanex.com
To make a certain text untranslatable, you just need to add one of the tags: "t", "notranslate", "shade". Here is an example from the text with the untranslatable world of Lingvanex:
Examples of use:
If you use "translateMode": "html":
Language | Language code | Language code with locale |
Afrikaans | af | af_ZA |
Albanian | sq | sq_AL |
Amharic | am | am_ET |
Arabic
|
ar
|
ar_AE |
ar_EG | ||
ar_SA | ||
Armenian | hy | hy_AM |
Azerbaijani | az | az_AZ |
Basque | eu | eu_ES |
Belarusian | be | be_BY |
Bengali | bn | bn_BD |
Bosnian | bs | bs_BA |
Bulgarian | bg | bg_BG |
Catalan | ca | ca_ES |
Cebuano | ceb | ceb_PH |
Chinese (Simplified) | zh-Hans | zh-Hans_CN |
Chinese (Traditional) | zh-Hant | zh-Hant_TW |
Corsican | co | co_FR |
Croatian | hr | hr_HR |
Czech | cs | cs_CZ |
Danish | da | da_DK |
Dutch | nl | nl_NL |
English
|
en
|
en_AU |
en_GB | ||
en_US | ||
Esperanto | eo | eo_WORLD |
Estonian | et | et_EE |
Finnish | fi | fi_FI |
French
|
fr
|
fr_CA |
fr_FR | ||
Frisian | fy | fy_NL |
Galician | gl | gl_ES |
Georgian | ka | ka_GE |
German | de | de_DE |
Greek | el | el_GR |
Gujarati | gu | gu_IN |
Haitian Creole | ht | ht_HT |
Hausa | ha | ha_NE |
Hawaiian | haw | haw_US |
Hebrew | he | he_IL |
Hindi | hi | hi_IN |
Hmong | hmn | hmn_CN |
Hungarian | hu | hu_HU |
Icelandic | is | is_IS |
Igbo | ig | ig_NG |
Indonesian | id | id_ID |
Irish | ga | ga_IE |
Italian | it | it_IT |
Japanese | ja | ja_JP |
Javanese | jv | jv_ID |
Kannada | kn | kn_IN |
Kazakh | kk | kk_KZ |
Khmer | km | km_KH |
Kinyarwanda | rw | rw_RW |
Korean | ko | ko_KR |
Kurdish (Kurmanji) | ku | ku_IR |
Kyrgyz | ky | ky_KG |
Lao | lo | lo_LA |
Latin | la | la_VAT |
Latvian | lv | lv_LV |
Lithuanian | lt | lt_LT |
Luxembourgish | lb | lb_LU |
Macedonian | mk | mk_MK |
Malagasy | mg | mg_MG |
Malay | ms | ms_MY |
Malayalam | ml | ml_IN |
Maltese | mt | mt_MT |
Maori | mi | mi_NZ |
Marathi | mr | mr_IN |
Mongolian | mn | mn_MN |
Myanmar (Burmese) | my | my_MM |
Nepali | ne | ne_NP |
Norwegian | no | no_NO |
Nyanja (Chichewa) | ny | ny_MW |
Odia (Oriya) | or | or_OR |
Pashto | ps | ps_AF |
Persian (Iranian) | fa | fa_IR |
Polish | pl | pl_PL |
Portuguese
|
pt
|
pt_BR |
pt_PT | ||
Punjabi (Panjabi) | pa | pa_PK |
Romanian | ro | ro_RO |
Russian | ru | ru_RU |
Samoan | sm | sm_WS |
Scots Gaelic | gd | gd_GB |
Serbian (Cyrillic) | sr-Cyrl | sr-Cyrl_RS |
Sesotho | st | st_LS |
Shona | sn | sn_ZW |
Sindhi | sd | sd_PK |
Sinhala (Sinhalese) | si | si_LK |
Slovak | sk | sk_SK |
Slovenian | sl | sl_SI |
Somali | so | so_SO |
Spanish
|
es
|
es_ES |
es_MX | ||
es_US | ||
Sundanese | su | su_ID |
Swahili | sw | sw_TZ |
Swedish | sv | sv_SE |
Tagalog (Filipino) | tl | tl_PH |
Tajik | tg | tg_TJ |
Tamil | ta | ta_IN |
Tatar | tt | tt_TT |
Telugu | te | te_IN |
Thai | th | th_TH |
Turkish | tr | tr_TR |
Turkmen | tk | tk_TM |
Ukrainian | uk | uk_UA |
Urdu | ur | ur_PK |
Uyghur | ug | ug_CN |
Uzbek | uz | uz_UZ |
Vietnamese | vi | vi_VN |
Welsh | cy | cy_GB |
Xhosa | xh | xh_ZA |
Yiddish | yi | yi_IL |
Yoruba | yo | yo_NG |
Zulu | zu | zu_ZA |
The API allows you to translate text from one language to another using a POST request.
Request body example:
{
"platform": "api",
"from": "en",
"to": "ko",
"enableTransliteration": false,
"data": "London is the capital and largest city of England and of the United Kingdom."
}
Translate Text - Endpoint Features
Object | Description |
---|---|
from |
[Required] — source language code in the format language_COUNTRY (for example: en_GB, es_ES, de_DE) or only the language code (for example: en, es, de). The language is indicated in lowercase letters, the country — in uppercase. |
to |
[Required] — translation language code in the format language_COUNTRY (for example: en_GB, es_ES, de_DE) or only the language code (for example: en, es, de). |
data |
[Required] — the text to be translated. |
enableTransliteration |
[Optional] — this parameter can take two values: true or false. When set to true, transliteration is enabled and the corresponding fields are returned in the response. When set to false, transliteration is disabled. The default value is false. |
{
"err": null,
"result": "런던은 영국과 영국의 수도이자 최대 도시입니다."
}
curl --location --request POST 'https://zylalabs.com/api/6440/lingvanex+translate+api/9266/translate+text?from=en&to=ko&data=If true, the response includes sourceTransliteration and targetTransliteration fields. This parameter can take two values: true or false. When set to true, transliteration is enabled and the corresponding fields are returned in the response. When set to false, transliteration is disabled. The default value is false.' --header 'Authorization: Bearer YOUR_API_KEY'
Translation of text arrays
Our API supports translation of not only individual phrases, but also entire text arrays. This allows you to efficiently process large amounts of data, translating several text elements at once in a single request. Ideal for localizing content in multiple languages, saving time and resources during mass translation.
Example of a request body for array translation:
{
"platform": "api",
"from": "en",
"to": "ko",
"data":[
"London is the capital and largest city of England and of the United Kingdom.",
"It stands on the River Thames in south-east England at the head of a 50-mile (80 km) estuary down to the North Sea, and has been a major settlement for two millennia.",
"The City of London, also known as the City, is a ceremonial county and local government district with city status in England."
]
}
Translate Array Text - Endpoint Features
Object | Description |
---|---|
from |
[Optional] Source language (for example, en). the language code in the format “language code_code of the country” from which the text is translated. The language code is represented only in lowercase letters, the country code only in uppercase letters (example en_GB, es_ES, ru_RU and etc.). If this parameter is not present, the auto-detect language mode is enabled |
to |
[Required] Target language (for example, de). language code in the format “language code_code of the country” to which the text is translated (required) |
data |
[Required] Text to be translated |
{
"err": null,
"result": [
"런던은 영국과 영국의 수도이자 최대 도시입니다.",
"이곳은 영국 남동부의 템스 강(북해까지 80km) 하구 머리 부분에 서 있으며 2000년 동안 주요 정착지였습니다.",
"City라고도 알려진 City of London은 영국에서 도시 지위를 가진 의례적인 카운티이자 지방 정부 구역입니다."
]
}
curl --location --request POST 'https://zylalabs.com/api/6440/lingvanex+translate+api/9297/translate+array+text?to=Required&data=Required' --header 'Authorization: Bearer YOUR_API_KEY'
The API allows you to translate text from one language to another, including the ability to automatically detect the language of the source text. A POST request is used for translation.
Request body example:
{
"platform": "api",
"to": "en",
"data": "긁기는 고양이의 ‘본능’.
"
}
Translation of text with automatic language detection - Endpoint Features
Object | Description |
---|---|
to |
[Required] — translation language code in the format language_COUNTRY (for example: en_GB, es_ES, de_DE) or only the language code (for example: en, es, de). |
data |
[Required] — the text to be translated. |
{
"err": null,
"result": "Scratching is a cat's ‘instinct’.",
"from": "ko"
}
curl --location --request POST 'https://zylalabs.com/api/6440/lingvanex+translate+api/9300/translation+of+text+with+automatic+language+detection?to=en&data=긁기는 고양이의 ‘본능’.' --header 'Authorization: Bearer YOUR_API_KEY'
Translation of HTML content
Our API supports translation of HTML content, allowing you to localize pages while preserving the HTML structure. To translate HTML, you need to activate the HTML translation mode by adding the parameter "translateMode": "html" to the request body.
Example request:
{
"platform": "api",
"from": "en",
"to": "de",
"translateMode": "html",
"data": "<ul><li>Hello</li><li>This is Translate HTML endpoint</li></ul>
"
}
Translate HTML - Endpoint Features
Object | Description |
---|---|
from |
[Optional] Source language (for example, en). the language code in the format “language code_code of the country” from which the text is translated. The language code is represented only in lowercase letters, the country code only in uppercase letters (example en_GB, es_ES, ru_RU and etc.). If this parameter is not present, the auto-detect language mode is enabled |
to |
[Required] Target language (for example, de). language code in the format “language code_code of the country” to which the text is translated (required) |
data |
[Required] Text to be translated |
{
"err": null,
"result": "<ul><li>Hallo</li><li>Das ist HTML-Endpunkt übersetzen</li></ul>"
}
curl --location --request POST 'https://zylalabs.com/api/6440/lingvanex+translate+api/9298/translate+html?from=en&to=de&data=- Hello
- This is Translate HTML endpoint
' --header 'Authorization: Bearer YOUR_API_KEY'
Request for supported languages
The API provides the ability to get a list of all supported languages. To do this, use a GET request, in which you must specify the code parameter — the language in which you want to receive a response (for example, "en" for English or "de " for German).
Example request:
GET https://api.example.com/v1/languages?code=en
The response will return a list of all supported languages with their codes and names in the selected language.
Get Supported Languages - Endpoint Features
Object | Description |
---|---|
code |
[Optional] the language code in the format “language code_code of the country”, which is used to display the names of the languages. The language code is represented only in lowercase letters, the country code only in uppercase letters (example en_GB, es_ES, ru_RU etc). If this option is not present, then English is used by default |
{
"err": null,
"result": [
{
"full_code": "af_ZA",
"code_alpha_1": "af",
"englishName": "Afrikaans",
"codeName": "Afrikaans",
"flagPath": "static/flags/afrikaans",
"testWordForSyntezis": "Hallo",
"rtl": "false",
"modes": [
{
"name": "Image object recognition",
"value": true
},
{
"name": "Image recognition",
"value": true
},
{
"name": "Translate web site",
"value": true
},
{
"name": "Translation",
"value": true
},
{
"name": "Translation document",
"value": true
}
]
},
....
{
"full_code": "zu_ZA",
"code_alpha_1": "zu",
"englishName": "Zulu",
"codeName": "Zulu",
"flagPath": "static/flags/afrikaans",
"testWordForSyntezis": "Sawubona",
"rtl": "false",
"modes": [
{
"name": "Image object recognition",
"value": true
},
{
"name": "Translate web site",
"value": true
},
{
"name": "Translation",
"value": true
},
{
"name": "Translation document",
"value": true
}
]
}
]
}
curl --location --request GET 'https://zylalabs.com/api/6440/lingvanex+translate+api/9299/get+supported+languages' --header 'Authorization: Bearer YOUR_API_KEY'
Header | Description |
---|---|
Authorization
|
[Required] Should be Bearer access_key . See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The Translate endpoint returns a JSON object containing the translation result. The key fields include "err," which indicates any error that occurred, and "result," which contains the translated text.
The Translate endpoint accepts three parameters: "from" (the source language code), "to" (the target language code), and "data" (the text to be translated). The "from" parameter is optional, enabling auto-detection of the source language.
The response data is structured as a JSON object. It includes an "err" field for error messages and a "result" field that holds the translated text. This structure allows for easy parsing and handling of the response.
Typical use cases include translating website content, localizing applications, and converting documents or audio files into different languages. The API is suitable for both personal and business translation needs.
Users can customize their requests by specifying the "from" and "to" language codes to control the translation direction. Additionally, they can input any text or HTML content in the "data" parameter for translation.
In the response, the "err" field indicates if there was an issue with the translation request (null if successful), while the "result" field contains the translated text. Users can check "err" to handle errors appropriately.
Data accuracy is maintained through advanced algorithms and continuous updates to the translation models. Lingvanex employs quality checks and user feedback to enhance translation quality over time.
The Translate endpoint provides translations of plain text and HTML content between over 100 languages. It supports various text formats, making it versatile for different translation needs.
You just need to add one of the tags: "t", "notranslate", "shade". An example of using these tags can be seen in "Info" on the Lingvanex Translate API page in the zylalabs .com service.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world’s most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the ‘X-Zyla-API-Calls-Monthly-Remaining’ field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.
To see the maximum number of API requests your plan allows, check the ‘X-Zyla-RateLimit-Limit’ response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.
The ‘X-Zyla-RateLimit-Reset’ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it’s important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.
Service Level:
100%
Response Time:
4,918ms
Service Level:
100%
Response Time:
344ms
Service Level:
100%
Response Time:
291ms
Service Level:
100%
Response Time:
180ms
Service Level:
100%
Response Time:
9,570ms
Service Level:
100%
Response Time:
5,008ms
Service Level:
100%
Response Time:
304ms
Service Level:
100%
Response Time:
1,400ms
Service Level:
100%
Response Time:
796ms
Service Level:
67%
Response Time:
1,500ms