---
title: "Papago Translation overview"
slug: "ai-naver-papagonmt"
tags: ["Papago Translation", "overview"]
updated: 2026-09-17T09:35:51Z
published: 2026-09-17T09:35:51Z
canonical: "api.ncloud-docs.com/ai-naver-papagonmt"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://api.ncloud-docs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Papago Translation overview

Available in Classic and VPC

Papago Translation is a NAVER Cloud Platform service that automatically translates languages from multiple countries (sources) to target languages through Neural Machine Translation (NMT) algorithm based on artificial neural networks. It provides APIs for text translation, document translation, web translation, language detection, and glossary features in RESTful form.

              Note

              

The Papago Translation API does not store users' source data or utilize it as training data.

## Common Papago Translation settings

The following describes commonly used request and response formats in Papago Translation APIs.

### Request

The following describes the common request format.

#### API URL

The request API URL is as follows:

```
Text Translation: https://papago.apigw.ntruss.com/nmt/v1
Doc Translation: https://papago.apigw.ntruss.com/doc-trans/v1
Website Translation: https://papago.apigw.ntruss.com/web-trans/v1
Language Detection: https://papago.apigw.ntruss.com/langs/v1
Glossary: https://papago.apigw.ntruss.com/glossary
```

#### Request headers

The following describes the headers.

| Field | Required | Description |
| --- | --- | --- |
| `x-ncp-apigw-api-key-id` | Required | Client ID issued after application registration in NAVER Cloud Platform console |
| `x-ncp-apigw-api-key` | Required | Client secret issued after application registration in NAVER Cloud Platform console |
| `Content-Type` | Conditional | Data type the client can handle - `application/json` \| `multipart/form-data` \| `application/x-www-form-urlencoded` - Text Translation: `application/json`, `application/x-www-form-urlencoded` - Doc Translation: `multipart/form-data` - Website Translation: `application/x-www-form-urlencoded` |

              Note

              

For information on how to register an application in the NAVER Cloud Platform console to obtain authentication information (client ID, client secret) required to use the API, see [APIs](https://guide.ncloud-docs.com/docs/en/papagotranslation-use-apis#Application%EB%93%B1%EB%A1%9D) in the Papago Translation user guide. If you do not select Papago Translation API after registering the application in the console, you will receive a 429 (Quota Exceed) error.

### Response

The following describes the common response format.

#### Response status codes

The following describes the response status codes.

              Note

              

For information about the HTTP status codes common to NAVER Cloud Platform, see [Ncloud API response status codes](/docs/en/common-ncpapi#3%EC%9D%91%EB%8B%B5%EC%83%81%ED%83%9C%EC%BD%94%EB%93%9C).

**Text Translation** The following describes the response status codes used by Text Translation.

| HTTP status code | Code | Message | Description |
| --- | --- | --- | --- |
| 400 | N2MT01 | source parameter is needed | `source` parameter missing |
| 400 | N2MT02 | Unsupported source language | `source` not supported |
| 400 | N2MT03 | target parameter is needed | `target` parameter missing |
| 400 | N2MT04 | Unsupported target language | `target` not supported |
| 400 | N2MT05 | source and target must be different | `source` and `target` are identical. |
| 400 | N2MT06 | There is no source-to-target translator | No `source` ⇒ `target` translator |
| 400 | N2MT07 | text parameter is needed | `text` parameter missing |
| 400 | N2MT08 | text parameter exceeds max length | `text` parameter exceeds the maximum allowable capacity. |
| 400 | N2MT09 | language detection failed | Failed to detect language |
| 400 | N2MT10 | invalid glossary key | Invalid `glossayKey` |
| 500 | N2MT99 | Internal server errors | Internal server error |

**Doc Translation** The following describes the response status codes used by Doc Translation.

| HTTP status code | Code | Message | Description |
| --- | --- | --- | --- |
| 400 | 00001 | Request is invalid | Invalid parameter exists. |
| 400 | 00006 | API call failed | Request to unsupported language pairs or file extensions |
| 401 | 25003 | requestId is invalid | - |
| 404 | 25006 | Not Found | - |
| 413 | 25004 | Request Entity Too Large | Exceeded allowed file size (up to 100 MB). |
| 429 | 25005 | Too many requests | Number of simultaneous translation requests exceeded |
| 500 | 00000 | API call failed | Internal server error |
| 500 | 25001 | API call failed | Internal server error |
| - | 01 | Error upload file to server | File upload failed |
| - | 10 | Translated Doc is empty | Empty text in the document file |
| - | 11 | Translated Docs length exceeded max-len | Exceeded the number of translatable characters in the document file. |
| - | 15 | Parsing is not possible | Parsing library failure (untranslatable file) |
| - | 16 | Unsupported source language | Unsupported source language |
| - | 17 | Detected langcode is the same as target langcode | Source and target languages are identical. |
| - | 18 | Language detection failed | Failed to detect language |
| - | 34 | maximum output size exceeded | Parser capacity exceeded. |
| - | 36 | PDF Resolution Error | Supported resolution exceeded |
| - | 37 | the target language is the same as the source language | Translation and document languages are identical. |
| - | 38 | invalid glossary key | Invalid `glossayKey` |
| - | 39 | pdf page length exceeded max size | Exceeded the number of translatable pages in the document file. |
| - | 41 | invalid hwpx file | Abnormal document |
| - | 50 | internal parser error | Internal parser error |
| - | 60 | internal server error | Internal server error |

**Website Translation** The following describes the response status codes used by Website Translation.

| HTTP status code | Code | Message | Description |
| --- | --- | --- | --- |
| 400 | 00001 | Request is invalid | `source`, `target`, and `html` parameters missing |
| 500 | 20001 | Source and target are equal | `source` and `target` languages are identical. |
| 400 | 20006 | Exceed max requests size allowed | `html` parameter exceeds the maximum allowable capacity. |
| 400 | N2MT02 | Unsupported source language | `source` not supported |
| 400 | N2MT04 | Unsupported target language | `target` not supported |
| 400 | N2MT05 | invalid glossary key | Invalid glossary key |
| 500 | 00000 | API call failed | Internal server error |

**Language Detection** The following describes the response status codes used by Language Detection.

| HTTP status code | Code | Message | Description |
| --- | --- | --- | --- |
| 400 | LD01 | Empty text | No `text` to detect the language |
| 400 | LD01 | Empty query parameter | No `text` to detect the language |
| 400 | LD03 | Query parameter exceeds max length | Exceeded the allowed length limit of `text` for language detection (up to 5000 characters). |
| 500 | LD99 | Internal server errors | Internal server error |

**Glossary** The following describes the response status codes used by Glossary.

| HTTP status code | Code | Message | Description |
| --- | --- | --- | --- |
| 204 | - | - | Glossary deletion completed |
| 400 | - | - | Invalid request |
| 400 | 10000 | INVALID_REQUEST | Invalid request (missing required parameters, etc.) |
| 400 | 20000 | NOT_FOUND_GLOSSARY | Glossary not found |
| 400 | 20004 | INVALID_GLOSSARY_KEY | Invalid `glossayKey` |
| 400 | 30000 | COUNT_LIMIT_OVER | Term registration count limit exceeded |
| 400 | 30005 | UNSUPPORTED_LANG | Unsupported language |
| 400 | 30006 | SAME_SOURCE_TARGET | The source and target languages are the same. |
| 400 | 30008 | Replacer already exists | Term already registered |
| 400 | 30009 | Unsupported character: , | It contains a special character `,` which can't be entered. |
| 400 | 30013 | INVALID_ARRAY_SIZE | The array is empty or exceeds 20 elements. |
| 400 | 30014 | INVALID_REPLACER_ID | Term not found (invalid ID) |
| 500 | 10001 | NTERNAL_ERROR | Server error |

## Papago Translation API

The following describes the APIs provided by the Papago Translation service.

| API | Description |
| --- | --- |
| [Text Translation > translation](/docs/en/ai-naver-papagonmt-translation) | Test translation |
| [Doc Translation > translation](/docs/en/ai-naver-papagodoctranslation-translate) | Document translation |
| [Doc Translation > status](/docs/en/ai-naver-papagodoctranslation-status) | Check document translation status. |
| [Doc Translation > download](/docs/en/ai-naver-papagodoctranslation-download) | Download document translation result. |
| [Website Translation > website translation](/docs/en/ai-naver-papagowebsitetranslation-translation) | Web translation |
| [Language Detection > detect](/docs/en/ai-naver-papagolanguagedetection-dect) | Detect language. |
| [Glossary > create](/docs/en/papago-createglossary) | Create glossary. |
| [Glossary > upload](/docs/en/papago-updateglossaryfile) | Upload glossary file. |
| [Glossary > download](/docs/en/papago-downloadglossaryfile) | Download glossary file. |
| [Glossary > get](/docs/en/papago-glossarylist) | Get glossary list. |
| [Glossary > delete](/docs/en/papago-deleteglossary) | Delete glossary. |

## Papago Translation related resources

NAVER Cloud Platform provides a variety of related resources to help users better understand Papago Translation APIs.

- Papago Translation API guides
  - [Create signature](/docs/en/common-ncpapi#1-%EC%9D%B8%EC%A6%9D%ED%82%A4-%EC%83%9D%EC%84%B1): How to create a signature to add to the request header
  - [Common Ncloud response status codes](/docs/en/common-ncpapi#3-%EC%9D%91%EB%8B%B5-%EC%83%81%ED%83%9C-%EC%BD%94%EB%93%9C): Information on common response status codes of NAVER Cloud Platform used by the Papago Translation service
  - [Cloud Insight user guide](https://guide.ncloud-docs.com/docs/en/cloudinsight-cloudinsightoverview): Introduction to how to request subscription to Cloud Insight required to set the application usage limits notifications and how to add notification recipients
  - [Sub Account User Guides](https://guide.ncloud-docs.com/docs/en/subaccount-overview): Introduction to how to use Sub Account that helps the management of Papago Translation's administration permissions
- How to use the Papago Translation service
  - [Papago Translation user guide](https://guide.ncloud-docs.com/docs/en/papagotranslation-overview): How to register applications, manage glossary, check usage, and set up notifications in NAVER Cloud Platform console
  - [Prerequisites for using Papago Translation](https://guide.ncloud-docs.com/docs/en/papagotranslation-spec): Introduction to environment specifications supported in Papago Translation, cautions for use, and pricing information
  - [Ncloud user environment guide](https://guide.ncloud-docs.com/docs/en/environment-environment-1-1): Explore VPC and Classic environments and supported services.
  - [Pricing and features](https://www.ncloud.com/product/aiService/papagoTranslation): View pricing details and key capabilities.
  - [Latest service news](https://www.ncloud.com/intro/news): The latest news on Papago Translation
  - [FAQs](https://www.ncloud.com/support/faq/prod?categoryCode2=AI&categoryCode3=SV_0055&page=1): Get answers to common Papago Translation questions.
  - [Contact Support](https://www.ncloud.com/support/question/service): Get help if you can't find what you need in the guide.