Papago · Schema
TranslationResponse
Response from the Papago NMT or SMT translation endpoint
TranslationNatural Language ProcessingMachine TranslationNeural Machine TranslationKoreanAsian LanguagesLocalizationLanguage Detection
Properties
| Name | Type | Description |
|---|---|---|
| message | object | Top-level response envelope |
JSON Schema
{
"$schema": "http://json-schema.org/draft-07/schema#",
"$id": "https://raw.githubusercontent.com/api-evangelist/papago/main/json-schema/translation-response.json",
"title": "TranslationResponse",
"description": "Response from the Papago NMT or SMT translation endpoint",
"type": "object",
"properties": {
"message": {
"type": "object",
"description": "Top-level response envelope",
"properties": {
"@type": {
"type": "string",
"example": "response"
},
"@service": {
"type": "string",
"example": "naverservice.nmt.proxy"
},
"@version": {
"type": "string",
"example": "1.0.0"
},
"result": {
"type": "object",
"description": "Translation result object",
"properties": {
"srcLangType": {
"type": "string",
"description": "Detected or specified source language code",
"example": "ko"
},
"tarLangType": {
"type": "string",
"description": "Target language code",
"example": "en"
},
"translatedText": {
"type": "string",
"description": "The translated output text",
"example": "I am Korean."
},
"engineType": {
"type": "string",
"description": "Translation engine identifier",
"example": "NMT",
"enum": ["NMT", "SMT"]
},
"pivot": {
"type": "string",
"description": "Pivot language used if translation used an intermediate language"
},
"dict": {
"type": "object",
"description": "Dictionary entry for the source term (if available)"
},
"tarDict": {
"type": "object",
"description": "Dictionary entry for the target term (if available)"
}
},
"required": ["srcLangType", "tarLangType", "translatedText"]
}
},
"required": ["result"]
}
},
"required": ["message"]
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/translation-response"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.