Identify the language behind any snippet of text.
Language Detector identifies the language of any submitted text string. It returns the primary language, its ISO 639-1 code, and candidate matches ranked by confidence scores.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"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"
}
]
}
}
About the Language Detector API
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.
What people use it for
- Inbound Ticket Dispatch
- When an international customer submits a support ticket, help desks inspect the text to route the ticket to native-speaking agents.
- Voice Synthesizer Selection
- To read articles aloud with correct accents, screen readers check the language code before choosing a matching text-to-speech voice model.
- Search Stemmer Configuration
- Tag document uploads with ISO language codes during ingest so search engines apply the correct grammatical stemming rules for each language.
- Market Research Segmentation
- Analytics teams group raw global survey responses by primary language before running regional sentiment and feedback models.
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Language Detector
Same data, same APIVerve account, same credit balance — one key works on all of them.
What information does Language Detector return for a text snippet?
What would 50,000 language detections cost me?
Is the confidence level included on the Free plan?
Does the response use standard ISO language codes?
Can I submit user-generated content like support tickets and reviews?
Request parameters — POST /v1/languagedetector
Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Required
| Parameter | Type | Example | Description |
|---|---|---|---|
textRequired | string | Guten Tag, wie geht es Ihnen? | The text to detect the language of |
curl -X POST "https://api.apiverve.com/v1/languagedetector" \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"esta es una frase en español. esta API puede detectar fácilmente el idioma"}'Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
content-typeRequired | POST body | application/json |
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.
Response — POST /v1/languagedetector
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"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] | Every candidate language considered, ranked from most to least likely | |
language | string | "spanish" | The candidate language's full name |
confidence | number | 0.38471794871794873 | How strongly the sample matched this language's trigram frequencies, from 0 to 1 |
code | string | "es" | ISO 639-1 code of this candidate language |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 2 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Language Detector calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 100 | Free |
| Starter | $29.99 | 200,000 | 100,000 | $0.30 |
| Pro | $99.99 | 1,000,000 | 500,000 | $0.20 |
| Mega | $299.99 | 4,000,000 | 2,000,000 | $0.15 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — POST /v1/languagedetector
No SDK to install — this is a plain HTTPS call to /v1/languagedetector with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/languagedetector" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — POST /v1/languagedetector
Install the Node.js SDK, then call the Language Detector API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/languagedetectorconst res = await fetch("https://api.apiverve.com/v1/languagedetector", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — POST /v1/languagedetector
Install the Python SDK, then call the Language Detector API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-languagedetectorimport requests
res = requests.get(
"https://api.apiverve.com/v1/languagedetector",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — POST /v1/languagedetector
Install the C# / .NET SDK, then call the Language Detector API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.LanguageDetectorusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/languagedetector");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — POST /v1/languagedetector
No SDK to install — this is a plain HTTPS call to /v1/languagedetector with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/languagedetector", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — POST /v1/languagedetector
No SDK to install — this is a plain HTTPS call to /v1/languagedetector with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/languagedetector");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — POST /v1/languagedetector
No SDK to install — this is a plain HTTPS call to /v1/languagedetector with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/languagedetector")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Language Detector form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Language Detector API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Language Detector API.