Directories
International codes
Coverage: Areas come from the official numbering plan of each edition’s country. Spain lists a province for every landline range; many other countries list their area codes and cities. Mobile numbers have no area in any country, and a few countries do not publish a plan we can read yet: there we only show the type of line.
Open toolOn this page
Purpose
Formats and supported calling codes only. They do not prove a number’s location, owner or active status. Some codes are shared.
Requirements
Anyone can read these guides, no account needed. Some tools require Pro, as indicated in each guide.
How to use it
Select the country edition, open the category or row you need and review the available details.
Calling codes
Country
Synthetic example
Invented example, not a real lookup. Do not call or open its links.
+1 · +44Interpret the result
Formats and supported calling codes only. They do not prove a number’s location, owner or active status. Some codes are shared.
Limitations
Formats and supported calling codes only. They do not prove a number’s location, owner or active status. Some codes are shared.
Troubleshooting
No matching countries
Use with the API
Needs an API key and credits. Each completed call costs 1 credit, even when there is no data. An active Pro account includes 20 credits per UTC calendar month, shared by every API route and spent first; unused monthly credits do not roll over. Credits bought on your account page work without Pro and never expire.
Errors are never charged: 401 invalid_api_key (missing or invalid key), 403 pro_required (no Pro credits and no purchased credits), 422 invalid input, 429 quota_exceeded (no credits left), rate_limit_exceeded or ai_busy (the AI of sms-check is at capacity), 503 tool_warming (the data is still being prepared) or tool or provider unavailable. After a 429 or 503, retry once the seconds in the Retry-After header have passed.
Search the ITU international calling codes by name, ISO code or dial code, with localised names. Exact dial-code and ISO matches come first.
Send the JSON body to the tool's own route, or to POST /v2/tools with the tool field added. Both routes return the same result.
POST https://api.nocall.io/v2/calling-codes
POST https://api.nocall.io/v2/tools {"tool":"calling-codes","query":"216","language":"en"}Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| query | string (1–40) | No | Country name, ISO code or calling code to search for. |
| language | string (enum, 33) | No (default: "en") | Language of the country names. |
REQUEST_ID="$(uuidgen)" && [ -n "$REQUEST_ID" ] &&
curl --request POST 'https://api.nocall.io/v2/calling-codes' \
--header "Authorization: Bearer $NOCALL_API_KEY" \
--header 'Content-Type: application/json' \
--header "Idempotency-Key: $REQUEST_ID" \
--data '{"query":"216","language":"en"}'import json
import os
import urllib.request
import uuid
api_key = os.environ.get('NOCALL_API_KEY')
if not api_key:
raise SystemExit('Set NOCALL_API_KEY')
request = urllib.request.Request(
'https://api.nocall.io/v2/calling-codes',
method='POST',
data=json.dumps({'query': '216', 'language': 'en'}).encode(),
headers={
'Authorization': 'Bearer ' + api_key,
'Content-Type': 'application/json',
'Idempotency-Key': str(uuid.uuid4()),
},
)
with urllib.request.urlopen(request, timeout=30) as response:
result = json.load(response)
print(result['data']['result'], result['meta']['unitsCharged'])import { randomUUID } from 'node:crypto';
const requestId = randomUUID();
const apiKey = process.env.NOCALL_API_KEY;
if (!apiKey) throw new Error('Set NOCALL_API_KEY');
const response = await fetch('https://api.nocall.io/v2/calling-codes', {
method: 'POST',
headers: {
Authorization: 'Bearer ' + apiKey,
'Content-Type': 'application/json',
'Idempotency-Key': requestId,
},
body: JSON.stringify({ query: '216', language: 'en' }),
});
const result = await response.json();
if (!response.ok) throw new Error(result.error?.code ?? 'request_failed');
console.log(result.data.result, result.meta.unitsCharged);Example response (200)
This is the documented example from the API reference. Lookups use a fictional number, and aggregates and AI answers show the shape of the result, not live data.
{
"data": {
"tool": "calling-codes",
"result": {
"rows": [
{
"code": "216",
"name": "Tunisia",
"territories": [
"Tunisia"
],
"source": "itu-e164-nnp-2026-08-09"
}
],
"total": 1
}
},
"meta": {
"requestId": "req_example",
"unitsCharged": 1,
"usage": {
"periodStart": "2026-10-01",
"unitLimit": 20,
"unitsUsed": 3,
"unitsRemaining": 17
}
}
}Result fields (data.result)
| Field | Type | Description |
|---|---|---|
| rows | array<object> | Matching calling codes with their localised name, territories and source; exact dial-code and ISO matches come first. |
| total | integer | Total number of matching rows. |