Overview
Translator works by using machine translation to convert text from one language to another. Models used are trained on large datasets to provide accurate translations.
Endpoint
One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.
curl -X POST https://api.apiverve.com/v1/translator \
-H "x-api-key: your_api_key_here" \
-H "Content-Type: application/json" \
-d '{
"text": "I'm so excited that tomorrow is going to be sunny! Can't wait!",
"source": "en",
"target": "es"
}'const res = await fetch('https://api.apiverve.com/v1/translator', {
method: 'POST',
headers: {
'x-api-key': 'your_api_key_here',
'Content-Type': 'application/json',
},
body: JSON.stringify({
"text": "I'm so excited that tomorrow is going to be sunny! Can't wait!",
"source": "en",
"target": "es"
}),
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.post(
"https://api.apiverve.com/v1/translator",
headers={"x-api-key": "your_api_key_here"},
json={
"text": "I'm so excited that tomorrow is going to be sunny! Can't wait!",
"source": "en",
"target": "es"
},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
"strings"
)
func main() {
body := strings.NewReader(`{
"text": "I'm so excited that tomorrow is going to be sunny! Can't wait!",
"source": "en",
"target": "es"
}`)
req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/translator", body)
req.Header.Set("Content-Type", "application/json")
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.
Authentication
Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Parameters
Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
textRequired | string | The text to translate length 0–50000 |
targetRequired | string | The language code to translate the text to (e.g., fr, es, de) length 0–10 |
sourceOptional | string | The language code of the text to translate (e.g., en). If left blank, language will be auto-detected |
Response
Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.
{
"status": "ok",
"error": null,
"data": {
"sourceLang": "en",
"targetLang": "es",
"translatedText": "¡Qué emoción que mañana hará sol! ¡Qué ganas!"
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
sourceLang | string | "en" | The detected or specified source language code |
targetLang | string | "es" | The target language code for translation output |
translatedText | string | "¡Qué emoción que mañana hará sol! ¡Qué ganas!" | The translated text in the target language |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
Start from a template
A working app built on this API, ready to deploy with your own key. Vercel asks for the key when you deploy; the code is on GitHub to change first.
Translator
Translate text between 18 languages, swap the direction in one click, and copy the result.
- Vue
- Vite
Use cases
- Live Agent Chat Translation
- When international customers message support in their native language, agents translate incoming tickets to draft localized replies without switching software.
- Catalog Description Localization
- Translate marketplace product titles and item descriptions into target consumer languages before launching digital storefronts in new overseas territories.
- App Store Review Translation
- Product teams convert foreign-language app store reviews into English using automatic language detection to monitor bug reports across regional markets.
- Internal Employee Announcement Translation
- To keep distributed staff updated, internal communicators render company-wide policy updates into multiple recipient languages for regional email distributions.
Other ways to use Translator
Set up Translator on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.
Related
More in Text Processing:
