- Print
- PDF
Papago Translation overview
- Print
- PDF
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, and you need to complete IAM authentication with API Gateway to call the APIs.
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://naveropenapi.apigw.ntruss.com/nmt/v1
Doc Translation: https://naveropenapi.apigw.ntruss.com/doc-trans/v1
Website Translation: https://naveropenapi.apigw.ntruss.com/web-trans/v1
Language Detection: https://naveropenapi.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
|
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 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.
For response status codes common to NAVER Cloud Platform, see Ncloud API response status codes.
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 errors |
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 | Unable to make simultaneous requests due to files being translated |
500 | 00000 | API call failed | Internal server errors |
500 | 25001 | API call failed | Internal server errors |
- | 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 |
- | 36 | PDF Resolution Error | Supported resolution exceeded |
- | 37 | the target language is the same as the source language | Translation and document languages are identical |
- | 50 | internal parser error | Internal parser error |
- | 60 | internal server error | Internal server errors |
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 |
500 | 00000 | API call failed | Internal server errors |
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 | Exceeds the allowed length limit of text for language detection (up to 5000 characters) |
500 | LD99 | Internal server errors | Internal server errors |
Glossary
The following describes the response status codes used by Glossary.
HTTP status code | Code | Message | Description |
---|---|---|---|
204 | - | - | Glossary deletion completed |
400 | - | - | Bad Request |
Papago Translation API
The following describes the APIs provided by the Papago Translation service.
API | Description |
---|---|
Text Translation > translation | Test translation |
Doc Translation > translation | Document translation |
Doc Translation > status | Check document translation status |
Doc Translation > download | Download document translation result |
Website Translation > website translation | Web translation |
Language Detection > detect | Detect language |
Glossary > create | Create glossary |
Glossary > upload | Upload glossary file |
Glossary > download | Download glossary file |
Glossary > get | Get glossary list |
Glossary > delete | 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: how to create a signature to add to the request header
- Common Ncloud response status codes: information on common response status codes of NAVER Cloud Platform used by the Papago Translation service
- Cloud Insight User Guide: 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 Guide: 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: how to register applications, manage glossary, check usage, and set up notifications in NAVER Cloud Platform console
- Prerequisites for using Papago Translation: introduction to environment specifications supported in Papago Translation, cautions for use, and pricing information
- Ncloud use environment guide: guide on VPC and Classic environments and supported features
- Introduction to pricing, characteristics, and detailed features: summary of Papago Translation pricing system, characteristics, and detailed features of Papago Translation
- Latest service news: the latest news on Papago Translation
- FAQ: frequently asked questions from Papago Translation users
- Contact Us: Send direct inquiries for unresolved questions that aren't answered by the guide.