Transliterate (2025-10-01-preview)

The Text transliteration API maps your source language script or alphabet to a target language script or alphabet. Unlike translation, transliteration doesn't return the meaning, only the way the text is written.

Request URL

Global endpoint configuration

Send a POST request to:

Windows

curl -X POST 'https://api.cognitive.microsofttranslator.com/transliterate?api-version=2025-10-01-preview&fromScript=Cyrl&toScript=Latn' ^
  --header 'Content-Type: application/json' ^
  --header 'Ocp-Apim-Subscription-Key: <your-resource-key>' ^
  --header 'Ocp-Apim-Subscription-Region: <your-resource-region>' ^
  --data '{
    "inputs": [
      {
        "text": "пример текста"
      }
    ]
}'

Linux or macOS

curl -X POST 'https://api.cognitive.microsofttranslator.com/transliterate?api-version=2025-10-01-preview&fromScript=Cyrl&toScript=Latn' \
  --header 'Content-Type: application/json' \
  --header 'Ocp-Apim-Subscription-Key: <your-resource-key>' \
  --header 'Ocp-Apim-Subscription-Region: <your-resource-region>' \
  --data '{
    "inputs": [
      {
        "text": "пример текста"
      }
    ]
}'

Custom endpoint configuration

Your custom domain endpoint is a URL formatted with your resource name and hostname and is available in the Azure portal. When you created your Translator resource, the value that you entered in the Name field is the custom domain name parameter for the endpoint.

Send a POST request:

Windows

curl -X POST 'https://<your-resource-name>.cognitiveservices.azure.com/translator/text/transliterate?api-version=2025-10-01-preview&fromScript=Cyrl&toScript=Latn&language=ru' ^
  --header 'content-type: application/json' ^
  --header 'ocp-apim-subscription-key: <your-resource-key>' ^
  --data '{
  "inputs": [
    {
      "Text": "пример текста"
    }
  ]
}'

Linux or macOS

curl -X POST 'https://<your-resource-name>.cognitiveservices.azure.com/translator/text/transliterate?api-version=2025-10-01-preview&fromScript=Cyrl&toScript=Latn&language=ru' \
  --header 'content-type: application/json' \
  --header 'ocp-apim-subscription-key: <your-resource-key>' \
  --data '{
  "inputs": [
    {
      "Text": "пример текста"
    }
  ]
}'

Private endpoint

For more information on Translator selected network and private endpoint configuration and support, see Virtual Network Support.

Request headers

Request parameters

Request parameters passed on the query string areas are as follows:

Request body

The body of the request is a JSON array named inputs. Each array element is a JSON object with a string property named Text, which represents the string to convert.

{
  "inputs": [
    {
      "Text": "пример текста"
    }
  ]
}

The following limitations apply:

• The array can have at most 10 elements.
• The text value of an array element can't exceed 1,000 characters including spaces.
• The entire text included in the request can't exceed 5,000 characters including spaces.

Response body

A successful response is a JSON array named value with one result for each element in the input array. A result object includes the following properties:

• text: A string that results from converting the input string to the output script.

• script: A string specifying the script used in the output.

An example JSON response is:

{
  "value": [
    {
      "text": "primer teksta",
      "script": "Latn"
    }
  ]
}

Response headers

Example

The following example shows how to convert two Japanese strings into Romanized Japanese.

  curl -X POST "https://api.cognitive.microsofttranslator.com/transliterate?api-version=2025-10-01-preview&language=ja&fromScript=Jpan&toScript=Latn" -H "X-ClientTraceId: 875030C7-5380-40B8-8A03-63DACCF69C11" -H "Ocp-Apim-Subscription-Key: <client-secret>" -H "Content-Type: application/json" -d @request.txt

The JSON payload for the request in this example:

{
  "inputs": [
      {
      "text": "こんにちは",
      "script": "jpan"
      },
      {
      "text": "さようなら",
      "script": "jpan"
      }
  ]
}

Response status codes

The following are the possible HTTP status codes that a request returns.

If an error occurs, the request also returns a JSON error response. The error code is a 6-digit number combining the 3-digit HTTP status code followed by a 3-digit number to further categorize the error. Common error codes can be found on the Status code reference page.

Next steps