{
"data": {
"languages": [
{
"code": "af",
"name": "Afrikaans"
},
{
"code": "sq",
"name": "Albanian"
},
{
"code": "am",
"name": "Amharic"
},
{
"code": "ar",
"name": "Arabic"
},
{
"code": "hy",
"name": "Armenian"
},
{
"code": "az",
"name": "Azerbaijani"
},
{
"code": "eu",
"name": "Basque"
},
{
"code": "be",
"name": "Belarusian"
},
{
"code": "bn",
"name": "Bengali"
},
{
"code": "bs",
"name": "Bosnian"
},
{
"code": "bg",
"name": "Bulgarian"
},
{
"code": "ca",
"name": "Catalan"
},
{
"code": "ceb",
"name": "Cebuano"
},
{
"code": "ny",
"name": "Chichewa"
},
{
"code": "zh-CN",
"name": "Chinese (Simplified)"
},
{
"code": "zh-TW",
"name": "Chinese (Traditional)"
},
{
"code": "co",
"name": "Corsican"
},
{
"code": "hr",
"name": "Croatian"
},
{
"code": "cs",
"name": "Czech"
},
{
"code": "da",
"name": "Danish"
},
{
"code": "nl",
"name": "Dutch"
},
{
"code": "en",
"name": "English"
},
{
"code": "eo",
"name": "Esperanto"
},
{
"code": "et",
"name": "Estonian"
},
{
"code": "tl",
"name": "Filipino"
},
{
"code": "fi",
"name": "Finnish"
},
{
"code": "fr",
"name": "French"
},
{
"code": "fy",
"name": "Frisian"
},
{
"code": "gl",
"name": "Galician"
},
{
"code": "ka",
"name": "Georgian"
},
{
"code": "de",
"name": "German"
},
{
"code": "el",
"name": "Greek"
},
{
"code": "gu",
"name": "Gujarati"
},
{
"code": "ht",
"name": "Haitian Creole"
},
{
"code": "ha",
"name": "Hausa"
},
{
"code": "haw",
"name": "Hawaiian"
},
{
"code": "iw",
"name": "Hebrew"
},
{
"code": "hi",
"name": "Hindi"
},
{
"code": "hmn",
"name": "Hmong"
},
{
"code": "hu",
"name": "Hungarian"
},
{
"code": "is",
"name": "Icelandic"
},
{
"code": "ig",
"name": "Igbo"
},
{
"code": "id",
"name": "Indonesian"
},
{
"code": "ga",
"name": "Irish"
},
{
"code": "it",
"name": "Italian"
},
{
"code": "ja",
"name": "Japanese"
},
{
"code": "jw",
"name": "Javanese"
},
{
"code": "kn",
"name": "Kannada"
},
{
"code": "kk",
"name": "Kazakh"
},
{
"code": "km",
"name": "Khmer"
},
{
"code": "rw",
"name": "Kinyarwanda"
},
{
"code": "ko",
"name": "Korean"
},
{
"code": "ku",
"name": "Kurdish (Kurmanji)"
},
{
"code": "ky",
"name": "Kyrgyz"
},
{
"code": "lo",
"name": "Lao"
},
{
"code": "la",
"name": "Latin"
},
{
"code": "lv",
"name": "Latvian"
},
{
"code": "lt",
"name": "Lithuanian"
},
{
"code": "lb",
"name": "Luxembourgish"
},
{
"code": "mk",
"name": "Macedonian"
},
{
"code": "mg",
"name": "Malagasy"
},
{
"code": "ms",
"name": "Malay"
},
{
"code": "ml",
"name": "Malayalam"
},
{
"code": "mt",
"name": "Maltese"
},
{
"code": "mi",
"name": "Maori"
},
{
"code": "mr",
"name": "Marathi"
},
{
"code": "mn",
"name": "Mongolian"
},
{
"code": "my",
"name": "Myanmar (Burmese)"
},
{
"code": "ne",
"name": "Nepali"
},
{
"code": "no",
"name": "Norwegian"
},
{
"code": "or",
"name": "Odia (Oriya)"
},
{
"code": "ps",
"name": "Pashto"
},
{
"code": "fa",
"name": "Persian"
},
{
"code": "pl",
"name": "Polish"
},
{
"code": "pt",
"name": "Portuguese"
},
{
"code": "pa",
"name": "Punjabi"
},
{
"code": "ro",
"name": "Romanian"
},
{
"code": "ru",
"name": "Russian"
},
{
"code": "sm",
"name": "Samoan"
},
{
"code": "gd",
"name": "Scots Gaelic"
},
{
"code": "sr",
"name": "Serbian"
},
{
"code": "st",
"name": "Sesotho"
},
{
"code": "sn",
"name": "Shona"
},
{
"code": "sd",
"name": "Sindhi"
},
{
"code": "si",
"name": "Sinhala"
},
{
"code": "sk",
"name": "Slovak"
},
{
"code": "sl",
"name": "Slovenian"
},
{
"code": "so",
"name": "Somali"
},
{
"code": "es",
"name": "Spanish"
},
{
"code": "su",
"name": "Sundanese"
},
{
"code": "sw",
"name": "Swahili"
},
{
"code": "sv",
"name": "Swedish"
},
{
"code": "tg",
"name": "Tajik"
},
{
"code": "ta",
"name": "Tamil"
},
{
"code": "tt",
"name": "Tatar"
},
{
"code": "te",
"name": "Telugu"
},
{
"code": "th",
"name": "Thai"
},
{
"code": "tr",
"name": "Turkish"
},
{
"code": "tk",
"name": "Turkmen"
},
{
"code": "uk",
"name": "Ukrainian"
},
{
"code": "ur",
"name": "Urdu"
},
{
"code": "ug",
"name": "Uyghur"
},
{
"code": "uz",
"name": "Uzbek"
},
{
"code": "vi",
"name": "Vietnamese"
},
{
"code": "cy",
"name": "Welsh"
},
{
"code": "xh",
"name": "Xhosa"
}]},"_note":"Response truncated for documentation purposes"}
curl --location --request GET 'https://pr213-testing.zylalabs.com/api/3114/linguistic+transformation+api/3302/languages+available' --header 'Authorization: Bearer YOUR_API_KEY'
{
"status": "success",
"data": {
"translatedText": "Siapa namamu?"
}
}
curl --location --request POST 'https://pr213-testing.zylalabs.com/api/3114/linguistic+transformation+api/3303/translator?source_language=en&target_language=id&text=What is your name' --header 'Authorization: Bearer YOUR_API_KEY'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Linguistic Transformation API simply include your bearer token in the Authorization header.
| 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.
(Save 2 months with annual billing 🎉)
Trusted by leading companies
Linguistic Transformation API is a powerful and versatile tool designed to bridge language barriers, allowing users to seamlessly integrate translation capabilities into their applications, websites or services. This application programming interface enables users to translate text from one language to another, facilitating effective communication on a global scale.
In essence, the Linguistic Transformation API acts as a language bridge, leveraging sophisticated machine learning algorithms to convert text between multiple languages accurately and efficiently. This functionality is invaluable to users operating in linguistically diverse environments, providing a means to connect with a wider audience, localize content and ensure that communication is effective and culturally relevant.
One of the key features of the Linguistic Transformation API is its ability to translate between a wide range of languages. Whether translating from English to Spanish, Chinese to French or any other language pair, the API offers a complete solution for breaking down language barriers. This flexibility is essential for companies with a global reach, allowing them to cater to diverse language preferences and tailor content to different target audiences.
Linguistic Transformation API goes beyond basic word-for-word translations and incorporates machine learning models that take context into account to produce more accurate and natural translations. This ensures that translated content maintains the desired meaning and tone, improving the overall quality of communication. The API's ability to handle context is especially crucial for industries such as marketing, customer service and content creation, where linguistic nuances play an important role.
In addition, the Linguistic Transformation API supports real-time translation, making it ideal for applications that require on-the-fly language conversion. Whether in chat applications, customer support systems or interactive websites, the API enables seamless communication through real-time text translation, enhancing the user experience and facilitating immediate understanding across language barriers.
For users, the Linguistic Transformation API offers a simple integration process, with well-defined endpoints that allow it to be easily incorporated into a variety of applications. The API supports both simple translation requests and more complex situations, such as batch processing or translation of large volumes of text. This flexibility meets the diverse needs of users, making it accessible for both small-scale applications and large-scale enterprise solutions.
The Linguistic Transformation API is a transformative tool for content localization, enabling users to extend their global reach and reach audiences in their native language. It is critical for breaking down language barriers in various industries, such as e-commerce, travel, education and healthcare, where effective communication is essential.
In conclusion, Linguistic Transformation API is a cornerstone in the field of multilingual communication. Its ability to provide accurate and contextualized translations between a multitude of languages makes it an invaluable asset for businesses and developers looking to create inclusive, accessible and globally connected applications and services. As the world becomes increasingly interconnected, Linguistic Transformation API is at the forefront, facilitating meaningful communication across linguistic boundaries.
It will receive parameters and provide you with a JSON.
Multilingual content localization: Localize content for websites, apps and marketing materials to serve a global audience and improve user engagement.
Real-time chat translation: Facilitate real-time translation in chat applications, enabling users of different languages to communicate seamlessly.
Global customer service: Implement language translation for customer service interactions, ensuring effective communication with customers around the world.
Language-independent data analysis: Analyze multilingual data sets using Linguistic Transformation API to understand sentiment, trends and patterns across multiple languages.
Cross-border e-commerce: Enable translation of product descriptions, reviews and customer interactions on e-commerce platforms for a global customer base.
Besides the number of API calls per month, there are no other limitations.
To use this API, users must indicate 2 languages and a text to obtain a text conversion.
The Linguistic Transformation API is a sophisticated tool designed to facilitate seamless language conversion, allowing users to integrate advanced language capabilities into their applications or services.
Zyla provides a wide range of integration methods for almost all programming languages. You can use these codes to integrate with your project as you need.
There are different plans suits everyone including a free trial for small amount of requests, but it’s rate is limit to prevent abuse of the service.
The GET Languages available endpoint returns a JSON object containing a list of supported languages. Each language entry includes a code (e.g., "en" for English) and the corresponding language name (e.g., "English").
The POST Translator endpoint response includes a "status" field indicating success or failure, and a "data" field containing the "translatedText," which is the translated version of the input text.
The response data is structured as a JSON object with a "data" key, which contains an array of language objects. Each object has "code" and "name" fields representing the language's code and its full name.
The POST Translator endpoint requires three parameters: the text to be translated, the source language code, and the target language code. For example, to translate "Hello" from English to Spanish, you would specify "en" and "es" as the language codes.
The GET Languages available endpoint provides information about all languages supported by the API, including their unique codes and names, allowing users to select appropriate languages for translation.
Users can utilize the "translatedText" field from the POST Translator response to display the translated content in their applications, ensuring that the communication is clear and contextually appropriate for the target audience.
Typical use cases include displaying a list of selectable languages in user interfaces, enabling users to choose their preferred language for translation, and ensuring that applications can support multilingual content.
Data accuracy is maintained through the use of advanced machine learning algorithms that consider context and linguistic nuances, ensuring that translations are not only accurate but also culturally relevant for the intended audience.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
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.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund