Country Lookup is a simple tool for looking up country data. It returns the country name, capital, and more.
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": {
// Country Lookup response payload
}
}
About the Country Lookup API
Country Lookup works by retrieving country data from various reliable sources and providing it in a structured format. The country database is updated regularly to ensure accurate and up-to-date information.
What people use it for
- Travel Planning
- Plan travel itineraries by using the Country Lookup API to get country data. Use the data to find information about countries, capitals, and more
- Geography Studies
- Study geography by using the Country Lookup API to get country data. Use the data to learn about countries, populations, and more
- International Business
- Conduct international business by using the Country Lookup API to get country data. Use the data to research markets and economic indicators
- Educational Purposes
- Use the Country Lookup API for educational purposes to teach students about countries and cultures. Provide students with information about countries and capitals
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 Country Lookup
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Country Lookup API do?
How do I authenticate Country Lookup API requests?
How much does the Country Lookup API cost?
How fast is the Country Lookup API?
What response formats does the Country Lookup API support?
What HTTP method does the Country Lookup API use?
Request parameters — GET /v1/countrylookup
Sent in the query string. 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 |
|---|---|---|---|
countryRequired | string | USA | The Country name or ISO code of the country for which you want to get the data (e.g., USA) |
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
majorcitiesOptionalPremium | boolean | true | Specify if you would like to return all major cities of the country found default false |
curl "https://api.apiverve.com/v1/countrylookup?country=USA&majorcities=true" \
-H "x-api-key: YOUR_API_KEY"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. |
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 — GET /v1/countrylookup
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": {
"search": "USA",
"countries": [
{
"name": {
"common": "United States",
"official": "United States of America",
"native": {
"eng": {
"official": "United States of America",
"common": "United States"
}
}
},
"tld": [
".us"
],
"cca2": "US",
"ccn3": "840",
"cca3": "USA",
"cioc": "USA",
"independent": true,
"status": "officially-assigned",
"capital": [
"Washington D.C."
],
"altSpellings": [
"US",
"USA",
"United States of America"
],
"region": "Americas",
"subregion": "North America",
"languages": {
"eng": "English"
},
"latlng": [
38,
-97
],
"landlocked": false,
"flag": "🇺🇸"
}
]
}
}
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 |
|---|---|---|---|
search | string | "USA" | The search term or country code used in the lookup request |
countries | array[1] | Array of country objects matching the search criteria | |
name | object | {...} | The country's names: common, official, and native forms |
common | string | "United States" | Common name of the country used in everyday reference |
official | string | "United States of America" | Official formal name of the country recognized internationally |
nativePremium | object | {...} | Native language names of the country keyed by language code |
engPremium | object | {...} | |
officialPremium | string | "United States of America" | |
commonPremium | string | "United States" | |
tld | array | [.us] | Top-level domains associated with the country |
cca2 | string | "US" | Two-letter country code following ISO 3166-1 alpha-2 standard |
ccn3Premium | string | "840" | Three-digit country code following ISO 3166-1 numeric standard |
cca3 | string | "USA" | Three-letter country code following ISO 3166-1 alpha-3 standard |
ciocPremium | string | "USA" | International Olympic Committee country code for sports competitions |
independentPremium | boolean | true | Indicates whether the country is politically independent |
statusPremium | string | "officially-assigned" | Official assignment status of the country code in international records |
capital | array | [Washington D.C.] | Array of capital city or cities of the country |
altSpellings | array | [US, ...] | Alternative spellings and abbreviations of the country name |
region | string | "Americas" | Geographic region where the country is located globally |
subregion | string | "North America" | More specific geographic subregion classification of the country |
languages | object | {...} | Object mapping language codes to official language names |
eng | string | "English" | |
latlngPremium | array | [38, ...] | Array with latitude and longitude coordinates for country center |
landlockedPremium | boolean | false | Indicates whether the country has no ocean or sea coastline |
flag | string | "🇺🇸" | Unicode flag emoji representation of the country |
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 | Country Lookup 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 — GET /v1/countrylookup
No SDK to install — this is a plain HTTPS call to /v1/countrylookup 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/countrylookup" \
-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 — GET /v1/countrylookup
Install the Node.js SDK, then call the Country Lookup API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/countrylookupconst res = await fetch("https://api.apiverve.com/v1/countrylookup", {
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 — GET /v1/countrylookup
Install the Python SDK, then call the Country Lookup API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-countrylookupimport requests
res = requests.get(
"https://api.apiverve.com/v1/countrylookup",
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 — GET /v1/countrylookup
Install the C# / .NET SDK, then call the Country Lookup 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.CountryLookupusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/countrylookup");
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 — GET /v1/countrylookup
No SDK to install — this is a plain HTTPS call to /v1/countrylookup 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/countrylookup", 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 — GET /v1/countrylookup
No SDK to install — this is a plain HTTPS call to /v1/countrylookup 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/countrylookup");
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 — GET /v1/countrylookup
No SDK to install — this is a plain HTTPS call to /v1/countrylookup 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/countrylookup")
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 Country Lookup 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 — Country Lookup 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 Country Lookup API.
Geography
- Cities Lookup
- Coordinates Are Sea
- Country Borders
- Country Boundaries
- Country Flags
- Country Languages
- Country Lookup
- County Data Lookup
- Distance Calculator
- Reverse Geocode
- State Boundaries
- USDA Hardiness Zone
- Zip Codes Lookup
Related articles
All articles →
Multi-Currency E-commerce: Stop Losing SalesShowing prices in local currency increases conversions 20-40%. Here's how to implement multi-currency pricing that actually works.Read
Location APIs: Distance, Geocoding, and TimezonesBuild location-aware features without Google Maps pricing. Distance calculations, address lookup, timezone handling—all from one API.Read
Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read