55世纪登录入口

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官网 彩神ll 3分快三app 彩神vlll官网 北京快3 大发彩票 彩神X 彩神5 神彩争霸app官方 55世纪 光大彩票注册平台 彩神8 神德正彩票 55世纪 彩神登陆 神彩争霸app官网 大发彩票 光大彩票注册平台 500彩票网 第1彩票 今日彩票网 彩神ll登录 福德彩票app下载 彩神llapp APP彩票 神彩争霸app官网 138彩票 彩神IV官方 彩神登陆 每日彩票 彩神iv 每日彩票平台 彩神llapp 彩神v8 神彩争霸8 神彩争霸app官网 第1彩票 大发彩票 500彩票网 凤凰彩票 彩神vlll官网 3分快三 极速快3 3分快3 每日彩票 178彩票网 光大彩票app下载登录 今日彩票 手机彩票 北京快3
烟台市| 弋阳县| 宝山区| 嘉禾县| 贡山| 高淳县| 永春县| 隆回县| 水城县| 巴青县| 郧西县| 肥西县| 白沙| 浮山县| 嘉定区| 徐水县| 扶绥县| 宁安市| 巴林左旗| 基隆市| 青神县| 隆化县| 岢岚县| 朝阳区| 公安县| 永新县| 万年县| 茌平县| 沅陵县| 平泉县| 新龙县| 桑日县| 轮台县| 乌恰县| 滦平县| 当涂县| 涞水县| 宜都市| 句容市| 瑞安市| 富裕县|