Find every country that shares a land border with any nation.
Country Borders identifies adjacent nations by two-letter ISO country code. It returns the list of bordering countries along with region, subregion, and landlocked status.
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": "Canada",
"cca2": "CA",
"landlocked": false,
"region": "Americas",
"subregion": "Northern America",
"coordinates": {
"lat": 60,
"lng": -95
},
"borders": [
"USA"
]
}
}
About the Country Borders API
Country Borders is a country border list lookup: pass a two-letter ISO country code and get back the neighboring countries that share a land boundary with it. The response names the country and adds its region, subregion and a landlocked country check, so one call answers both who are this country's neighbors and whether it has access to the sea.
Travel and logistics apps use it to suggest overland routes and cross-border options, education and quiz apps use it for geography questions, and data teams use the bordering countries list to group or compare adjacent nations in maps and reports.
The Free plan returns the country name, its ISO code, region, subregion, landlocked flag and the full list of borders. Paid plans add a latitude and longitude for the requested country, a representative center point that is handy for placing a marker or centring a map on the country you looked up.
How it works
The country parameter takes an ISO 3166-1 alpha-2 code such as CA or de; it is trimmed and uppercased before lookup. The code is resolved against a country code reference, then matched to a world countries dataset for the common name, the landlocked flag and the center coordinates, and finally to a borders dataset keyed by the same two-letter code. A code that fails any of these steps returns a 404 with country not found.
borders lists each neighbor by its three-letter ISO 3166-1 alpha-3 code, for example ["USA"] for Canada, rather than by name. Map them to names with a country lookup if you need to display them. The list covers land borders only; when the dataset records no land neighbors for a country, the array is empty.
country is the common English name and cca2 the two-letter code. region and subregion come from the borders dataset and use broad groupings such as Americas and Northern America for Canada. landlocked is true when the country has no coastline.
coordinates.lat and coordinates.lng are the country's representative point from the world countries dataset, often rounded to whole degrees (Canada is 60, -95). Treat them as a point to centre a map on, not as a geometric centroid or a capital city location. They are null on the Free plan; every other field is returned on all plans.
What people use it for
- Cross-Border Route Planning
- Freight dispatchers check adjacent nations along transport corridors to verify transit jurisdictions and identify landlocked destinations needing sea-port rerouting.
- Regional Market Expansion
- E-commerce platforms identify neighboring territories around existing warehouses to sequence regional delivery coverage country by country.
- Geopolitical Strategy Games
- Game developers build realistic adjacency maps between territories to enforce valid troop movements across shared national borders.
- Compliance Risk Screening
- When auditing vendor supply chains, trade compliance officers flag suppliers operating adjacent to sanctioned territories.
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 Borders
Same data, same APIVerve account, same credit balance — one key works on all of them.
Can I query a country using its full name instead of an ISO code?
Does the API report whether a country is landlocked?
Are country center point coordinates included on the Free plan?
How far does the Starter plan go for country border lookups?
Can I use the border data in a commercial mapping or logistics app?
Request parameters — GET /v1/countryborders
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 | CA | The Country 2 Letter ISO code (e.g., CA) length 2-2 |
curl "https://api.apiverve.com/v1/countryborders?country=CA" \
-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/countryborders
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": {
"country": "Canada",
"cca2": "CA",
"landlocked": false,
"region": "Americas",
"subregion": "Northern America",
"coordinates": {
"lat": 60,
"lng": -95
},
"borders": [
"USA"
]
}
}
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 |
|---|---|---|---|
country | string | "Canada" | Full name of the country |
cca2 | string | "CA" | Two-letter ISO country code |
landlocked | boolean | false | Indicates if country is landlocked without ocean access |
region | string | "Americas" | Geographic continent or major world region |
subregion | string | "Northern America" | More specific geographic subdivision within region |
coordinates | object | {...} | |
latPremium | number | 60 | Latitude coordinate of country center point |
lngPremium | number | -95 | Longitude coordinate of country center point |
borders | array | [USA] | List of neighboring country names that share borders |
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 Borders 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/countryborders
No SDK to install — this is a plain HTTPS call to /v1/countryborders 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/countryborders" \
-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/countryborders
Install the Node.js SDK, then call the Country Borders API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/countrybordersconst res = await fetch("https://api.apiverve.com/v1/countryborders", {
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/countryborders
Install the Python SDK, then call the Country Borders API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-countrybordersimport requests
res = requests.get(
"https://api.apiverve.com/v1/countryborders",
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/countryborders
Install the C# / .NET SDK, then call the Country Borders 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.CountryBordersusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/countryborders");
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/countryborders
No SDK to install — this is a plain HTTPS call to /v1/countryborders 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/countryborders", 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/countryborders
No SDK to install — this is a plain HTTPS call to /v1/countryborders 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/countryborders");
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/countryborders
No SDK to install — this is a plain HTTPS call to /v1/countryborders 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/countryborders")
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 Borders 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 Borders 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 Borders API.
Geography
- Cities Lookup
- Coordinates Are Sea
- Country Borders
- Country Boundaries
- Country Flags
- Country Languages
- Country Lookup
- County Data Lookup
- Distance Calculator
- India Pincode Lookup
- 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