[
{
"zones": [
{
"zone": 1,
"description": "North American Numbering Plan (NANP)"
},
{
"zone": 2,
"description": "Mostly Africa"
},
{
"zone": 3,
"description": "Mostly Europe"
},
{
"zone": 4,
"description": "Mostly Europe"
},
{
"zone": 5,
"description": "South and Central Americas"
},
{
"zone": 6,
"description": "Southeast Asia and Oceania"
},
{
"zone": 7,
"description": "Russia and neighboring regions"
},
{
"zone": 8,
"description": "East Asia, Southeast Asia, and special services"
},
{
"zone": 9,
"description": "West, Central, and South Asia, and part of Southern Europe"
}
]
}
]
curl --location --request POST 'https://pr213-testing.zylalabs.com/api/9976/global+telephone+codes+api/18929/get+zones' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
[
{
"zone": "Zone 5: South and Central Americas",
"description": "Countries in South and Central Americas",
"countries": [
"Falkland Islands",
"Belize",
"Guatemala",
"El Salvador",
"Honduras",
"Nicaragua",
"Costa Rica",
"Panama",
"Saint-Pierre and Miquelon",
"Haiti",
"Peru",
"Mexico",
"Cuba",
"Argentina",
"Brazil",
"Chile",
"Colombia",
"Venezuela",
"Guadeloupe",
"Bolivia",
"Guyana",
"Ecuador",
"French Guiana",
"Paraguay",
"Martinique",
"Suriname",
"Uruguay",
"Sint Eustatius",
"Saba",
"Bonaire",
"Curaçao"
]
}
]
curl --location --request POST 'https://pr213-testing.zylalabs.com/api/9976/global+telephone+codes+api/18935/get+countries+by+zone' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"zone":"Required"}'
[
{
"country": "Brazil",
"dialing_code": "55",
"iso_code": "BR"
}
]
curl --location --request POST 'https://pr213-testing.zylalabs.com/api/9976/global+telephone+codes+api/18940/search+dialing+codes+by+country' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"country":"Required"}'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Global Telephone Codes API simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
Required
Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.
|
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
(Save 2 months with annual billing 🎉)
Trusted by leading companies
The Global Telephone Codes API specializes in providing detailed information about international dialing codes for countries around the world. It processes data fields such as country name, ISO country code and dialing code.. Each entry in the API's dataset includes structured information that adheres to international standards for telecommunications, ensuring accuracy and consistency. The API supports formats like JSON for data exchange, making it easy to integrate with various applications. Users can expect to retrieve data in a schema that includes fields for country identification, dialing code, and region classification, allowing for straightforward querying and filtering. Technical requirements include a stable internet connection and adherence to rate limits to ensure optimal performance. The API is designed to handle requests efficiently, providing quick responses for applications requiring real-time access to phone code information, which is essential for telecommunications, travel, and international business operations.
The Global Telephone Codes API provides comprehensive data on international dialing codes, including country name, ISO country code, and dialing code.
The API delivers data in JSON format, which allows for easy integration with various applications and facilitates straightforward data exchange.
The API can be used in telecommunications applications, travel booking systems, and international business operations where accurate dialing information is essential.
The API's output schema includes fields for country identification, dialing code, and region classification, allowing users to query and filter data effectively.
Developers can integrate the API by making HTTP requests to retrieve dialing information, utilizing the structured JSON responses to enhance user experience in applications requiring phone code data.
The "get zones" endpoint returns a list of telecommunications zones, each with a unique zone number and a description. This helps users understand the geographical classification of countries based on their dialing codes.
The "get countries by zone" endpoint requires a zone parameter, which can be obtained from the "get zones" endpoint. This allows users to filter countries based on specific telecommunications zones.
The response from the "search dialing codes by country" endpoint is organized as an array of objects, each containing the country name, its dialing code, and ISO code. This structure allows for easy access to relevant dialing information.
The "get countries by zone" endpoint provides a list of countries within a specified zone, along with a description of that zone. This helps users identify which countries fall under particular telecommunications classifications.
The key fields in the response data include "country" (the name of the country), "dialing_code" (the international dialing code), and "iso_code" (the ISO country code). These fields provide essential information for telecommunications.
Users can utilize the returned data from the "get zones" endpoint to understand the geographical classification of dialing codes, which can assist in developing applications that require accurate dialing information based on user location.
The Global Telephone Codes API ensures data accuracy by adhering to international telecommunications standards and regularly updating its dataset. This helps maintain consistency and reliability in the information provided.
Typical use cases include integrating dialing code information into communication applications, enhancing travel booking systems with accurate country codes, and supporting international business operations that require precise dialing information.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund