<bdo id="hbzhp"></bdo>
        <track id="hbzhp"><div id="hbzhp"><em id="hbzhp"></em></div></track>

          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.

          富豪彩票 快三下载 网盟彩票平台 178彩票 APP彩票网 快三购买平台 光大彩票app下载登录 彩神ll手机版下载 网盟彩票网 彩神ll手机版下载 彩神VI 网信彩票 优信彩票 一分快3彩票 神彩争霸8|谁与争锋 极速快三平台 神彩争霸8最新版本下载 手机购彩 神彩争霸app官网 极速快3app 优信彩票网 每日彩票平台 彩神v在线登录 一分快3 彩票大赢家 光大彩票网 55世纪平台 第1彩票 神彩争霸8 彩神登陆 神彩争霸app官方 网信彩票网 彩神V 十三水游戏 神彩争霸app官方 手机十三水 好运彩彩票网 快三下载 优信彩票 第1彩票 神彩争霸app官网 神彩争霸8最新版本下载 彩神v在线登录 快三信誉平台 神彩争霸下载旧版 光大彩票注册平台 极速快3app 第1彩票 彩神8app下载安装 彩神v8 138彩票 优信彩票网 55世纪 网信彩票 一分快三网站 极速快三官网 富豪彩票 vip彩票网 网信彩票 VIP彩票平台 彩神8 138彩票 彩神iv争霸 快三 神彩争霸8官方网站 光大彩票app下载登录 500彩票 每日彩票平台 今日彩票 彩1彩票app下载 快三购买平台 网盟彩票app 3分快三app 彩神vlll vip彩票网 一分快3 光大彩票注册平台 网盟彩票 极速快三平台 快三购买平台 178彩票 每日彩票平台 彩神X 3分快三 神德正彩票 每日彩票 神彩争霸app官网 彩神VI 彩神登陆 APP彩票网 神彩争霸app官网 快三 178彩票 一分快三网站 178彩票网 每日彩票 178彩票网 彩神登陆 彩神登陆