<track id="zhkbv"><div id="zhkbv"></div></track>
        1. <tbody id="zhkbv"><div id="zhkbv"><td id="zhkbv"></td></div></tbody>

          <option id="zhkbv"></option>
          1. <bdo id="zhkbv"></bdo>

            The Lewene API?

            Welcome to the Lewene API documentation. Here you’ll find links to various client libraries, details about our API and a complete list of endpoints available.

            If you have any problems or requests please contact our support team at any time and we’ll be happy to help!

            Typically we find that the Lewene API is used in one of two situations:

            • ? You have a large amount of content that would benefit from a simple API workflow
            • ? You would like to offer translation to your end-users

            Keeping this in mind, let’s take a look at what key considerations exist in both cases.

            High volume needs?

            Lewene’s API is specifically designed to accept large volumes of content that gets queued, processed and passed onto a human translator.

            We recommend submitting multiple orders within a single request. Jobs within an order will be worked on by a single translator per language pair. For quick turnaround, we recommend keeping order sizes between 500-2000 words per order, as these are nice bite-size pieces of content that a translator can typically complete within a single day. For consistency, we also recommend keeping related content within a single order (e.g. product titles, descriptions, and their attributes).

            When dealing with such a large volume of content it’s especially important to develop good instructions for our translators. This will go a long way in maintaining a high level of consistency and keep the quality of translations as high as possible. Please contact our support team if you’d like help.

            Providing translation to your users?

            Lewene’s service can be completely white labeled if needed, but we also encourage you to advertise Lewene as a translation partner.

            The most important step in providing translation to a customer is soliciting the right information about the content from them. For example, if you were to develop a platform for translating a Twitter feed, it would be important to ask your users about the tone of the content (e.g. formal or casual), the end purpose of the translation (e.g. business or personal) and a description of the feed/business itself. All of this content can be passed on through our API and helps our translators understand the context of the content.

            Our GET /translate/service/languages/ end point will provide an up-to-date list of supported languages that should be used rather than any hardcoding.

            The POST /translate/service/quote/ end point can be used to generate a cost estimate for the content. Note that this may require several requests be summed together if the number of jobs being submitted is high.

            In most situations, it’s best to charge your users directly for the translations while we will charge your account.

            Next steps?

            Once you’ve had a chance to read the API visual guide take a look at the API overview to get a more detailed understanding of our platform.


            老版彩神ll 178彩票 老版彩神ll 神彩争霸8|谁与争锋 极速快三 彩神登陆 神彩争霸8|谁与争锋 彩神登陆 彩神vlll 凤凰彩票 彩神6 神彩争霸app官网 彩神vlll 168彩票网 500彩票网 APP彩票 彩神VI 大发彩票 神彩争霸8|谁与争锋 今日彩票 快三 每日彩票平台 神彩争霸8最新版本下载 今日彩票 178彩票网 168彩票 彩神1 手机十三水 快三下载 手机十三水 北京快3 1分快3 彩神1 神彩争霸8最新版本下载 彩神X 神彩争霸app官方 十三水游戏 神德正彩票 神彩争霸8最新版本下载 神德正彩票 大发彩票网 快三下载 大发彩票 第1彩票网 凤凰彩票 幸运快三彩票 第1彩票 彩票大赢家 神德正彩票 手机彩票 凤凰彩票 神彩争霸8 彩神登陆 彩神IV官方 光大彩票app下载登录 彩票app 快三信誉平台 神彩争霸app官网 网盟彩票 神彩争霸app官方 极速快三官网 老版彩神ll 彩神llapp 极速快三官网 北京快3 优信彩票 彩神llapp 网信彩票 彩神8app下载安装 178彩票 老版彩神ll 优信彩票网 3分快三app APP彩票网 手机十三水 彩神IV官方 凤凰彩票 富豪彩票网 彩神8 快三 彩神ll平台 神彩争霸app官网 网盟彩票网 光大彩票注册平台 彩神ll争霸 快三信誉平台 快三下载 彩神vlll 大发彩票 彩神ll 彩神VI 手机彩票网 极速快三 178彩票网 大发彩票网 网盟彩票app 神彩争霸8|谁与争锋 神彩争霸app官网 神彩争霸app官网