Overview
Language Detector works by analyzing the text and comparing it to a database of languages and ai models. It uses advanced algorithms to detect the language of the text and returns the language code and the confidence level.
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/languagedetector \
-H "x-api-key: your_api_key_here" \
-H "Content-Type: application/json" \
-d '{
"text": "esta es una frase en español. esta API puede detectar fácilmente el idioma"
}'const res = await fetch('https://api.apiverve.com/v1/languagedetector', {
method: 'POST',
headers: {
'x-api-key': 'your_api_key_here',
'Content-Type': 'application/json',
},
body: JSON.stringify({
"text": "esta es una frase en español. esta API puede detectar fácilmente el idioma"
}),
});
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/languagedetector",
headers={"x-api-key": "your_api_key_here"},
json={
"text": "esta es una frase en español. esta API puede detectar fácilmente el idioma"
},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
"strings"
)
func main() {
body := strings.NewReader(`{
"text": "esta es una frase en español. esta API puede detectar fácilmente el idioma"
}`)
req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/languagedetector", 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 detect the language of |
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": {
"primaryLanguage": "spanish",
"primaryCode": "es",
"confidenceLevel": "medium",
"detectedLanguages": [
{
"language": "spanish",
"confidence": 0.38471794871794873,
"code": "es"
},
{
"language": "portuguese",
"confidence": 0.2946153846153846,
"code": "pt"
},
{
"language": "danish",
"confidence": 0.2464615384615384,
"code": "da"
}
]
}
}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 |
|---|---|---|---|
primaryLanguage | string | "spanish" | The most likely detected language |
primaryCode | string | "es" | ISO 639-1 code of the primary language |
confidenceLevelPremium | string | "medium" | Overall confidence level: high, medium, or low |
detectedLanguages | array[3] | ||
language | string | "spanish" | |
confidence | number | 0.38471794871794873 | |
code | string | "es" |
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. |
Use cases
- Content Moderation
- Use the Language Detector API to detect the language of text for content moderation. Use the data to filter out inappropriate content and maintain community standards
- Multilingual Support
- Detect languages by using the Language Detector API to support multilingual content. Use the data to provide language-specific features, translations, and user experiences
- Text Analysis
- Analyze text by using the Language Detector API to detect the language of text. Use the data to study language patterns, sentiment analysis, and text classification
- Language Learning
- Learn languages by using the Language Detector API to detect the language of text. Use the data to explore word meanings, expand vocabulary, and improve language skills
Other ways to use Language Detector
Set up Language Detector 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 AI/Computer Vision: