Country Languages API
Overview
To use Country Languages, you need an API key. You can get one by creating a free account and visiting your dashboard.
GET Endpoint
https://api.apiverve.com/v1/countrylanguagesExample
How to call the Country Languages API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/countrylanguages?name=ZW" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/countrylanguages?name=ZW', {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
response = requests.get('https://api.apiverve.com/v1/countrylanguages?name=ZW', headers=headers)
data = response.json()
print(data)package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/countrylanguages?name=ZW", nil)
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": {
"country": "ZW",
"name": "Zimbabwe",
"officialName": "Republic of Zimbabwe",
"officialLanguages": [
"Chibarwe",
"English",
"Kalanga",
"Khoisan",
"Ndau",
"Northern Ndebele",
"Chewa",
"Shona",
"Sotho",
"Tonga",
"Tswana",
"Tsonga",
"Venda",
"Xhosa",
"Zimbabwean Sign Language"
],
"officialLanguageCount": 15
}
}Authentication
The Country Languages 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 Country Languages API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the Country Languages API:
Get Official Country Languages
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
name | string | required | The Country 2 letter ISO code for which you want to get languages for data (e.g., ZW) | - |
Response
The Country Languages 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>
<country>ZW</country>
<name>Zimbabwe</name>
<officialName>Republic of Zimbabwe</officialName>
<officialLanguages>
<officialLanguage>Chibarwe</officialLanguage>
<officialLanguage>English</officialLanguage>
<officialLanguage>Kalanga</officialLanguage>
<officialLanguage>Khoisan</officialLanguage>
<officialLanguage>Ndau</officialLanguage>
<officialLanguage>Northern Ndebele</officialLanguage>
<officialLanguage>Chewa</officialLanguage>
<officialLanguage>Shona</officialLanguage>
<officialLanguage>Sotho</officialLanguage>
<officialLanguage>Tonga</officialLanguage>
<officialLanguage>Tswana</officialLanguage>
<officialLanguage>Tsonga</officialLanguage>
<officialLanguage>Venda</officialLanguage>
<officialLanguage>Xhosa</officialLanguage>
<officialLanguage>Zimbabwean Sign Language</officialLanguage>
</officialLanguages>
<officialLanguageCount>15</officialLanguageCount>
</data>
</response>
status: ok
error: null
data:
country: ZW
name: Zimbabwe
officialName: Republic of Zimbabwe
officialLanguages:
- Chibarwe
- English
- Kalanga
- Khoisan
- Ndau
- Northern Ndebele
- Chewa
- Shona
- Sotho
- Tonga
- Tswana
- Tsonga
- Venda
- Xhosa
- Zimbabwean Sign Language
officialLanguageCount: 15
| key | value |
|---|---|
| country | ZW |
| name | Zimbabwe |
| officialName | Republic of Zimbabwe |
| officialLanguages | [Chibarwe,English,Kalanga,Khoisan,Ndau,Northern Ndebele,Chewa,Shona,Sotho,Tonga,Tswana,Tsonga,Venda,Xhosa,Zimbabwean Sign Language] |
| officialLanguageCount | 15 |
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 |
|---|---|---|---|
country | string | The 2-letter ISO country code for the requested country | |
name | string | The common name of the country | |
officialName | string | The official formal name of the country | |
officialLanguages | array | Array of official and commonly spoken languages in the country | |
officialLanguageCount | number | Total count of official and commonly spoken languages |
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 Country Languages through GraphQL to combine it with other API calls in a single request. Query only the country languages 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 {
countrylanguages(
input: {
name: "ZW"
}
) {
country
name
officialName
officialLanguages
officialLanguageCount
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Country Languages 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
Country Languages 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 Country Languages 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 Country Languages
Official Country Languages packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Country Languages 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 Country Languages?
How many credits does Country Languages cost?
Each successful Country Languages 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 country languages lookups.
Can I use Country Languages in production?
The free plan is for testing and development only. For production use of Country Languages, 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 Country Languages from a browser?
What happens if I exceed my Country Languages credit limit?
When you reach your monthly credit limit, Country Languages 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.








