Language Detector API
Overview
To use Language Detector, you need an API key. You can get one by creating a free account and visiting your dashboard.
POST Endpoint
https://api.apiverve.com/v1/languagedetectorExample
How to call the Language Detector API in different programming languages.
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 response = 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"
})
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
payload = {
"text": "esta es una frase en español. esta API puede detectar fácilmente el idioma"
}
response = requests.post('https://api.apiverve.com/v1/languagedetector', headers=headers, json=payload)
data = response.json()
print(data)package main
import (
"fmt"
"io"
"net/http"
"bytes"
"encoding/json"
)
func main() {
payload := map[string]interface{}{
"text": "esta es una frase en español. esta API puede detectar fácilmente el idioma"
}
jsonPayload, _ := json.Marshal(payload)
req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/languagedetector", bytes.NewBuffer(jsonPayload))
req.Header.Set("X-API-Key", "your_api_key_here")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}{
"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"
}
]
}
}Authentication
The Language Detector API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the Language Detector API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the Language Detector API:
Detect Language
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
text | string | required | The text to detect the language of | - |
Response
The Language Detector API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<primaryLanguage>spanish</primaryLanguage>
<primaryCode>es</primaryCode>
<confidenceLevel>medium</confidenceLevel>
<detectedLanguages>
<detectedLanguage>
<language>spanish</language>
<confidence>0.38471794871794873</confidence>
<code>es</code>
</detectedLanguage>
<detectedLanguage>
<language>portuguese</language>
<confidence>0.2946153846153846</confidence>
<code>pt</code>
</detectedLanguage>
<detectedLanguage>
<language>danish</language>
<confidence>0.2464615384615384</confidence>
<code>da</code>
</detectedLanguage>
</detectedLanguages>
</data>
</response>
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
| key | value |
|---|---|
| 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 Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
primaryLanguage | string | The most likely detected language | |
primaryCode | string | ISO 639-1 code of the primary language | |
confidenceLevelPremium | string | Overall confidence level: high, medium, or low | |
| [ ] Array items: | array[3] | - | |
â”” language | string | - | |
â”” confidence | number | - | |
â”” code | string | - |
Headers
Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →
GraphQL AccessALPHA
Access Language Detector through GraphQL to combine it with other API calls in a single request. Query only the language detector data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
languagedetector(
input: {
text: "esta es una frase en español. esta API puede detectar fácilmente el idioma"
}
) {
primaryLanguage
primaryCode
confidenceLevel
detectedLanguages
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Language Detector API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →
Rate Limiting
Language Detector requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →
Error Codes
The Language Detector API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →
SDKs for Language Detector
Official Language Detector packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Language Detector works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for Language Detector?
How many credits does Language Detector cost?
Each successful Language Detector API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful language detector lookups.
Can I use Language Detector in production?
The free plan is for testing and development only. For production use of Language Detector, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use Language Detector from a browser?
What happens if I exceed my Language Detector credit limit?
When you reach your monthly credit limit, Language Detector API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.








