Text Translation

This describes the web services that relate to text translation.

Aculab Cloud uses Google Translate to perform text translation.

• Translate
• Supported Languages

• Translate

  This API takes a PUT or POST request with the text to be translated in the request body. The text must be submitted as plain text encoded in utf-8. The maximum content size is 102400 characters. The URL parameters are used to specify the source and target language codes.

  Authorisation

  This API uses basic authentication, using your cloud account username and API Access Key.

  Username	:	cloudID/username (e.g. 1-2-0/bob@example.com)
  Password	:	API Access key

  Request:

  Url	:	https://ws.aculabcloud.net/translate/v1/translate
  Methods	:	PUT, POST

  
  

  Parameter	Required/Optional	Description
  target_language	required	The language code of the intended translation Use a language code from Translation Languages.
  source_language	optional	The language code of the source text. If not specified the source language will be detected. However we recommend specifying the source language to improve accuracy. Use a language code from Translation Languages.

  Returns:

  A JSON object with the following parameters:

  Parameter	Type	Availability	Description
  request_id	string	always	a unique ID for this request.
  target_language_name	string	always	the English name of the requested target language.
  detected_source_language	string	when the request has not specified a source language	the language code of the detected source language.
  source_language_name	string	always	the English name of the requested or detected source language.
  translation	string	always	the translated text.

  Example:

  https://ws.aculabcloud.net/translate/v1/translate?target_language=es

  With the body containing "The text to be translated".

  Response:

    {
      "request_id": "tr-23b2cc6d_1.0066bcb579.000008",
      "target_language_name": "Spanish",
      "detected_source_language": "en",
      "source_language_name": "English",
      "translation": "El texto a traducir"
    }

• Supported Languages

  This returns a list of objects detailing the supported languages.

  Authorisation

  This API uses basic authentication, using your cloud account username and API Access Key.

  Username	:	cloudID/username (e.g. 1-2-0/bob@example.com)
  Password	:	API Access key

  Request:

  Url	:	https://ws.aculabcloud.net/translate/v1/supported_languages
  Methods	:	GET

  Returns:

  A JSON array of objects describing the supported languages. The objects have the following parameters:

  Parameter	Type	Description
  language_name	string	the English name of the language.
  language	string	the language code of the language.

  Example:

  https://ws.aculabcloud.net/translate/v1/supported_languages

  Response:

    [
      {
          "language_name": "Abkhaz",
          "language": "ab"
      },
      {
          "language_name": "Acehnese",
          "language": "ace"
      },
      ...
      {
          "language_name": "Zapotec",
          "language": "zap"
      },
      {
          "language_name": "Zulu",
          "language": "zu"
      }
    ]

Translation Languages

Aculab Cloud Translation supports over 240 languages. All of these languages can be used with text translation.

During live audio translation (e.g. using the Connect action with translator), speech is first converted to text using Speech Recognition. The translator then converts the text from the speech recognition language to text in the language that the Text To Speech (TTS) voice requires. It then uses TTS to play back the translated speech.

The table below shows the languages that can be used for text translation. It also details which speech recognition languages produce text that can be used as source text for each translation language and which TTS voices expect input text in each translation language.

sip header

Describes a SIP header. SIP headers can be sent by a connect or an answer action. If the service has been configured to report received SIP headers, any matching SIP headers will be included in the call info.

Used in class call info.

Used by actions answer and connect.

Only non-standard SIP headers should be sent. Sending standard SIP headers will usually cause the call to fail.

The handling of non-standard SIP headers is dependent on the entities the SIP messages pass through, such as proxies and back-to-back user agents, and the receiving SIP endpoint. It is recommended that only a single header of each name is sent and that all names are prefixed with "X-". This will increase the likelyhood of the headers reaching the intended target.

language wrappers and examples

It contains the following properties: