今日彩票网

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.


极速快三 APP彩票平台 福德彩票app下载 彩神llapp 优信彩票 彩神v在线登录 大发彩票 手机十三水 3分快3 彩神登陆 网盟彩票平台 500彩票网 手机彩票 3分快3 优信彩票 手机彩票 55世纪官网 彩神v8 网盟彩票平台 彩神V 彩神llapp 优信彩票网 极速快三平台 幸运快三彩票 老版彩神ll 神彩争霸8|谁与争锋 神彩争霸app官网 1分快3 幸运快三彩票 彩神vlll 神彩争霸app官方 神彩争霸8|谁与争锋 vip彩票网 快三 手机彩票 富豪彩票网 极速快3 幸运飞艇平台 彩神8app下载安装 每日彩票 vip彩票 彩票app 彩神vlll 彩神登陆 手机购彩 彩神IV官方 极速快三平台 彩神登陆 彩神ll
永嘉县| 甘洛县| 富宁县| 元朗区| 瑞金市| 南雄市| 沙雅县| 皋兰县| 台山市| 辽阳市| 新竹县| 巩义市| 台安县| 马龙县| 怀柔区| 余江县| 孟连| 遂昌县| 新和县| 黄山市| 米易县| 镇平县| 句容市| 木兰县| 孝义市| 察雅县| 北海市| 大邑县| 苍梧县| 定兴县| 钟山县| 龙井市| 合江县| 潮州市| 成武县| 广丰县| 中卫市| 雅江县| 綦江县| 武功县| 连南|