Login
      Contents x
      Papago Translation overview
        • Print
        • PDF
        Contents

        Papago Translation overview

          • Print
          • PDF
          Article summary

          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

          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.

          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://naveropenapi.apigw.ntruss.com/nmt/v1
Doc Translation: https://naveropenapi.apigw.ntruss.com/doc-transs/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.

          FieldRequiredDescription
          x-ncp-apigw-api-key-idRequiredClient ID issued after application registration in NAVER Cloud Platform console
          x-ncp-apigw-api-keyRequiredClient secret issued after application registration in NAVER Cloud Platform console
          Content-TypeConditionalData 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 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 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 codeCodeMessageDescription
          400N2MT01source parameter is neededsource parameter missing
          400N2MT02Unsupported source languagesource not supported
          400N2MT03target parameter is neededtarget parameter missing
          400N2MT04Unsupported target languagetarget not supported
          400N2MT05source and target must be differentsource and target are identical
          400N2MT06There is no source-to-target translatorNo source ⇒ target translator
          400N2MT07text parameter is neededtext parameter missing
          400N2MT08text parameter exceeds max lengthtext parameter exceeds the maximum allowable capacity
          400N2MT09language detection failedFailed to detect language
          400N2MT10invalid glossary keyInvalid glossayKey
          500N2MT99Internal server errorsInternal server errors

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

          HTTP status codeCodeMessageDescription
          40000001Request is invalidInvalid parameter exists
          40000006API call failedRequest to unsupported language pairs or file extensions
          40125003requestId is invalid-
          40425006Not Found-
          41325004Request Entity Too LargeExceeded allowed file size (up to 100 MB)
          42925005Too many requestsUnable to make simultaneous requests due to files being translated
          50000000API call failedInternal server errors
          50025001API call failedInternal server errors
          -01Error upload file to serverFile upload failed
          -10Translated Doc is emptyEmpty text in the document file
          -11Translated Docs length exceeded max-lenExceeded the number of translatable characters in the document file
          -15Parsing is not possibleParsing library failure (untranslatable file)
          -16Unsupported source languageUnsupported source language
          -17Detected langcode is the same as target langcodeSource and target languages are identical
          -18Language detection failedFailed to detect language
          -50internal parser errorInternal parser error
          -60internal server errorInternal server errors

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

          HTTP status codeCodeMessageDescription
          40000001Request is invalidsource, target, and html parameters missing
          50020001Source and target are equalsource and target languages are identical
          40020006Exceed max requests size allowedhtml parameter exceeds the maximum allowable capacity
          400N2MT02Unsupported source languagesource not supported
          400N2MT04Unsupported target languagetarget not supported
          50000000API call failedInternal server errors

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

          HTTP status codeCodeMessageDescription
          400LD01Empty textNo text to detect the language
          400LD01Empty query parameterNo text to detect the language
          400LD03Query parameter exceeds max lengthExceeds the allowed length limit of text for language detection (up to 5000 characters)
          500LD99Internal server errorsInternal server errors

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

          HTTP status codeCodeMessageDescription
          204--Glossary deletion completed
          400--Bad Request

          Papago Translation API

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

          APIDescription
          Text Translation > translationTest translation
          Doc Translation > translationDocument translation
          Doc Translation > statusCheck document translation status
          Doc Translation > downloadDownload document translation result
          Website Translation > website translationWeb translation
          Language Detection > detectDetect language
          Glossary > createCreate glossary
          Glossary > uploadUpload glossary file
          Glossary > downloadDownload glossary file
          Glossary > getGet glossary list
          Glossary > deleteDelete glossary

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

          Was this article helpful?
          What's Next
          Change password!
          Changing your password will log you out immediately. Use the new password to log back in.
          Change profile
          Success!
          First name must have atleast 2 characters. Numbers and special characters are not allowed.
          Last name must have atleast 1 characters. Numbers and special characters are not allowed.
          Enter a valid email
          Enter a valid password
          Your profile has been successfully updated.
          Logout