Live Chat Translation

Introduction

Live Chat Translation is specifically developed for multi-language conversation scenarios in the e-commerce field, achieving accurate translation among 33 different languages. It leverages e-commerce-specific data training to enhance translation quality and is equipped with custom intervention features, providing efficient multi-language market expansion solutions for e-commerce platforms and developers.

Use Cases

Live Chat Translation can be used to translate dialogue content, knowledge bases, and other materials in the international e-commerce field. Compared to other similar products, it offers superior localization expression in e-commerce scenarios.

The following are samples of translating English e-commerce dialogue content into Spanish:

Input	Aidge Output	Competitor Output	Aidge Advantages
IS that youri tem?	¿Es ese tu artículo?	¿Ese es tu Tem?	Automatically correct spelling errors and achieve precise translation.
Oh i'm very sorry to hear that may i know your order number to check please?	Oh, lamento mucho escuchar eso. ¿Podría saber su número de pedido para verificar, por favor?	Oh, lamento mucho saber que puedo saber su número de pedido para verificar por favor.	Considering the context for sentence breaks, it can accurately translate even if users do not use punctuation where they should.
Also as per check	También, según la verificación	También según el cheque	Focus on differences in country-specific expressions.
May I request for your order number please so I can check it further at our end?	¿Podría proporcionarme su número de pedido para que pueda verificarlo más a fondo desde nuestro lado?	¿Puedo solicitar su número de pedido, por favor, para poder verificarlo más detalladamente desde nuestro lado?	In conversation scenarios, more attention is given to the politeness of the translation.

Pricing

To use the API, you are required to choose and purchase an API resource pack from us on a subscription basis.

• Each resource pack is valid for one calendar year upon successful purchase, and enables you to access the API up to the number of requests specified in the pack. No refunds can be provided.

• If you need to purchase more QPS due to business requirements, please contact us via navigation bar or email us ([e-mail]).

• Resource packs cannot be used across different products. For example, if you need to use both product text translation and image translation, you must purchase separate resource packs for each.

Capacity	Price (USD)	Unit Price(USD)	Maximum QPS
10 million characters	150	$15.0 /million characters	15
100 million characters	1350	$13.5 /million characters	15
1 billion characters	12000	$12.0 /million characters	15

Key Features

1. Supported languages and scenarios

You can choose any two languages from the table below as the source and target languages for translation. For example, translate content from English to French.

Support Language	Language Code	Comment
English	en
Spanish	es
French	fr
Portuguese	pt
Korean	ko
Chinese	zh	As the source language, it supports a mix of Simplified Chinese and English. As target language, it could output simplified Chinese.
Arabic	ar
German	de
Italian	it
Turkish	tr
Vietnamese	vi
Bahasa Indonesia	id
Urdu Pakistan	ur	As the source language, it supports a mix of Roman and English. As target language, it could output Roman.
Polish	pl
Dutch	nl
Japanese	ja
Ukrainian	uk
Thai	th
Malay	ms
Bengali	bn	As the source language, it supports a mix of Roman and native and English. As target language, it could output Roman.
Greek	el
Romanian	ro
Hungarian	hu
Czech	cs
Sinhalese	si
Nepali	ne	As the source language, it supports a mix of Roman and English. As target language, it could output native.
Hebrew	he
Russian	ru
Finnish	fi
Hindi	hi
Burmese	my
Swedish	sv
Azerbaijani	az

2. Supported Text Formats

Now text and html format are supported.

3. Supports Language Recognition

It supports the identification between a single source language and English. For example, if the input language is potentially Spanish or English, the product will first identify whether the source language is Spanish or English, and then start translating.

Note that source language recognition only supports languages between a single non-English and English. If the input languages consists of Spanish and French, the interface will prompt an error.

4. Support Long Text Input

When the input content is long text, it will automatically split the text to ensure that the length of the translated text does not exceed the translation model's limit (750 characters). It supports two types of text delimiters.

1. Line breaks

2. User-Defined Delimiters：${new_session}，Users can forcibly insert delimiters in the source text. The system will split the text accordingly and then perform the translation.

5. Supports Content Risk Control.

For translation content that contains security risks, it will automatically abort the output of the result.

6. Supported Intervention Ability

Through creating an intervention glossary, you can intervene in the target translation results to more precisely meet the translation needs of different scenarios. Simply associate the corresponding intervention glossary ID in the input parameters to achieve the intervention.

Uploading custom intervention glossaries is not supported now. If needed, please contact us via navigation bar or email us ([e-mail]).

7. Source Language Detection

In cases where the source language is unknown, users can enter "auto" and the system will automatically identify the source language. The translation will then be performed based on the detected language, which will be included in the output parameters.

Quick Start

1. Sample Request

Text Length Limit: When the length of the text, excluding line breaks and user-defined delimiters, exceeds the translation length limit, an error indicating that the text is too long will be prompted.

Five key parameters need to be entered: source text, source language, target language, and text format type. Optional input includes: intervention glossary ID.

Java

IopClient client = new IopClient(url, appkey, appSecret);
IopRequest request = new IopRequest();
request.setApiName("/ai/chat/translation/and/polishment");
request.addApiParameter("sourceTextList", "[\"¿Cómo puedo obtener un reembolso?\",\"¿Qué puedo hacer por ti?\"]");
request.addApiParameter("sourceLanguage", "es");
request.addApiParameter("targetLanguage", "en");
request.addApiParameter("formatType", "text");
request.addApiParameter("glossary", "test_glossory");
request.addApiParameter("extension", "{}");
IopResponse response = client.execute(request);
System.out.println(response.getBody());
Thread.sleep(10);

2. Sample Response

• The output of translation:

With different input parameters, the model will return different translated content.

Java

{
  "data": {
    "usage": 57,
    "translated": [
      "How can I get a refund?",
      "What can I do for you?"
    ],
    "class": "com.aidc.service.api.client.translate.dto.CommonTranslationResponse"
  },
  "requestId": "21413d5a17193029202356783eb7e5",
  "success": true,
  "resCode": 200,
  "resMessage": "success",
  "code": "0",
  "request_id": "21410ad417193029202356958",
  "_trace_id_": "21413d5a17193029202356783eb7e5"
}

FAQ

1. What languages does the Livechat translation API support?

You can refer to "supported language pairs". More languages are being added. If you have any needs, please contact us via navigation bar or Email [e-mail] us via navigation bar or email us ([e-mail]).

2. How is the API priced?

It is priced based on the number of characters translated. For details, please refer to the "Pricing".

3. Does the intervention capability support batch activation?

Yes. You only need to associate multiple intervention glossary IDs that will be available. However, uploading custom intervention glossaries is not supported now. If you have any needs, please contact us via navigation bar or email us ([e-mail]).

4. What performance-related information needs to be confirmed when integrating?

The maximum QPS of interface is 15. If it's more than 15, please contact us via navigation bar or email us ([e-mail]) to confirm the following information and prepare resources in advance.

• Confirm SLA （Service Level Agreement，such as AVG RT / P99 RT / AVG QPS / maximum QPS in different languages.

• Is it possible to provide Badcase to help improve the model's translation quality?

We highly encourage you to provide Badcase to continuously improve the translation quality. Please contact us via navigation bar or email us ([e-mail]).

Appendix

Language Code

Language Code use ISO 639-1 code. For country/region variants of languages, the table follows the RFC 5646 format, which adds an underline and then theISO 3166 two-letter country/region code. For example, the language code for Traditional Chinese is zh-tw.