Text translation

The latest service changes have not yet been reflected in this content. We will update the content as soon as possible. Please refer to the Korean version for information on the latest updates.

Available in Classic and VPC

Translate and output entered text. The output results can be supplemented with glossary, honorific translation, and term replacement options.

Request

This section describes the request format. The method and URI are as follows:

Request headers

For information about the headers common to all Papago Translation APIs, see Common Papago Translation headers.

Request body

You can include the following data in the body of your request:

<span translate="no"> </span> or <span class="notranslate"> </span>

Languages supported for translation

The following describes the supported languages for translation.

Request example

The request example is as follows:

If Content-Type: application/x-www-form-urlencoded

The following is a sample request when the request header Content-Type is application/x-www-form-urlencoded.

curl --location --request POST
'https://papago.apigw.ntruss.com/nmt/v1/translation' \
--header 'X-NCP-APIGW-API-KEY-ID: {Client ID issued when registering the app}' \
--header 'X-NCP-APIGW-API-KEY: {Client secret issued when registering the app}' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'source=auto' \
--data-urlencode 'target=en' \
--data-urlencode 'text=Hello, I like to eat apples while riding my bike.'

For Content-Type: application/json

The request example if the request header's Content-Type is application/json is as follows:

curl --location --request POST
'https://papago.apigw.ntruss.com/nmt/v1/translation' \
--header 'X-NCP-APIGW-API-KEY-ID: {Client ID issued when registering the app}' \
--header 'X-NCP-APIGW-API-KEY: {Client secret issued when registering the app}' \
--header 'Content-Type: application/json' \
--data '{
    "source": "auto",
    "target": "ko",
    "text": "Advanced technology requires numerous beta tests and feedbacks. This process takes up a lot of time, but it must be done for development.",
    "glossaryKey": "{glossaryKey}",
    "replaceInfo": " ",
    "honorific": "true"
}'

Response

This section describes the response format.

Response body

The response body includes the following data:

Response status codes

For information about the HTTP status codes common to all Papago Translation APIs, see Common Papago Translation response status codes.

Response example

The response example is as follows:

{
    "message": {
        "result": {
            "srcLangType": "ko",
            "tarLangType": "en",
            "translatedText": "Hello, I like to eat apple while riding a bicycle."
        }
    }
}