The Geographical Codes API is the ultimate solution for accessing accurate and up-to-date ISO codes for countries and their subdivisions. Designed to streamline your application's data management, the API allows users, developers, businesses and researchers to effortlessly retrieve ISO country and subdivision codes, simplifying geographic data management and enabling better global understanding.
The Geographical Codes API has been created to meet the diverse needs of different industries, from e-commerce and logistics to finance and academic research. It serves as a fundamental tool for accessing essential information that underpins countless location-based services, legal requirements and data analysis applications around the world.
At the core of this API is a comprehensive and regularly updated database of ISO 3166-1 and ISO 3166-2 codes, which maintains data accuracy and currency to ensure you always have access to the latest information. These standardized codes are essential for identifying countries and their subdivisions in a consistent and universally recognized format, facilitating the integration and exchange of data between different platforms and systems.
The intuitive and user-friendly design of the API ensures seamless integration into your applications. With clear and well-documented endpoints, you can effortlessly retrieve ISO country codes, saving valuable development time and resources. Whether you are an experienced developer or just starting out, implementing the API into your project is a smooth process.
The Geographical Codes API is highly available and reliable, allowing you to access data with fast and accurate response time. Our state-of-the-art infrastructure ensures that your application can reliably retrieve ISO codes at any time, ensuring a smooth user experience for your customers and users.
In summary, the Geographical Codes API is a versatile and indispensable tool for accessing ISO country and subdivision codes. It enables developers and companies to streamline data management, optimize global operations and meet legal requirements. With its up-to-date database, ease of integration and robust security, the API lays the foundation for enhanced location-based services, global research and effective data analysis. Harness the power of ISO codes with the Geographical Codes API and take your application to new heights in the interconnected world.
It will receive parameters and provide you with a JSON.
Address validation: E-commerce platforms and logistics companies can use the API to validate and standardize customer addresses, ensuring accurate and efficient delivery of goods worldwide.
International shipping: Companies can leverage ISO codes to facilitate international shipments by automatically completing customs documents and complying with country-specific regulations.
Multilingual Web sites: Web sites serving a global audience can display country and subdivision names in different languages based on ISO codes, improving user experience and localization.
Financial transactions: Financial institutions can use ISO codes to identify countries and subdivisions to process cross-border transactions, complying with international banking regulations.
Academic research: Researchers and academics can use the API to organize and analyze data for global studies, regional comparisons and international collaborations.
Basic Plan: 600 API Calls. 3 requests per second.
Pro Plan: 1,500 API Calls. 3 requests per second.
Pro Plus Plan: 5,500 API Calls. 3 requests per second.
To use this endpoint you must indicate in the parameter the name of a country.
Get ISO codes by country - Endpoint Features
Object | Description |
---|---|
name |
[Required] |
[{"name":"Germany","alpha2Code":"DE","alpha3Code":"DEU","numericCode":"276"}]
curl --location --request GET 'https://zylalabs.com/api/2338/geographical+codes+api/2251/get+iso+codes+by+country?name=Germany' --header 'Authorization: Bearer YOUR_API_KEY'
To use this endpoint you must indicate in the parameter an ISO 2 code.
Get country by ISO two code - Endpoint Features
Object | Description |
---|---|
alpha2Code |
[Required] |
[{"name":"United States of America","alpha2Code":"US","alpha3Code":"USA","numericCode":"840"}]
curl --location --request GET 'https://zylalabs.com/api/2338/geographical+codes+api/2252/get+country+by+iso+two+code?alpha2Code=US' --header 'Authorization: Bearer YOUR_API_KEY'
To use this endpoint you must indicate in the parameter an ISO three code.
Get country by ISO three code - Endpoint Features
Object | Description |
---|---|
alpha3Code |
[Required] |
[{"name":"United States of America","alpha2Code":"US","alpha3Code":"USA","numericCode":"840"}]
curl --location --request GET 'https://zylalabs.com/api/2338/geographical+codes+api/2253/get+country+by+iso+three+code?alpha3Code=USA' --header 'Authorization: Bearer YOUR_API_KEY'
To use this endpoint you must indicate in the parameter an ISO 2 code.
Get all country subdivisions - Endpoint Features
Object | Description |
---|---|
iso2code |
[Required] |
[{"name":"Baden-WΓΌrttemberg","code":"DE-BW","category":"Land"},{"name":"Bayern","code":"DE-BY","category":"Land"},{"name":"Berlin","code":"DE-BE","category":"Land"},{"name":"Brandenburg","code":"DE-BB","category":"Land"},{"name":"Bremen","code":"DE-HB","category":"Land"},{"name":"Hamburg","code":"DE-HH","category":"Land"},{"name":"Hessen","code":"DE-HE","category":"Land"},{"name":"Mecklenburg-Vorpommern","code":"DE-MV","category":"Land"},{"name":"Niedersachsen","code":"DE-NI","category":"Land"},{"name":"Nordrhein-Westfalen","code":"DE-NW","category":"Land"},{"name":"Rheinland-Pfalz","code":"DE-RP","category":"Land"},{"name":"Saarland","code":"DE-SL","category":"Land"},{"name":"Sachsen","code":"DE-SN","category":"Land"},{"name":"Sachsen-Anhalt","code":"DE-ST","category":"Land"},{"name":"Schleswig-Holstein","code":"DE-SH","category":"Land"},{"name":"ThΓΌringen","code":"DE-TH","category":"Land"}]
curl --location --request GET 'https://zylalabs.com/api/2338/geographical+codes+api/2254/get+all+country+subdivisions?iso2code=DE' --header 'Authorization: Bearer YOUR_API_KEY'
Header | Description |
---|---|
Authorization
|
[Required] Should be Bearer access_key . See "Your API Access Key" above when you are subscribed. |
No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.
There are different plans suits everyone including a free plan for small amount of requests per day, but itβs rate is limit to prevent abuse of the service.
Zyla provides a wide range of integration methods for almost all programming languages. You can use these codes to integrate with your project as you need.
The Geographical Codes API is a tool to easily access ISO codes for countries and subdivisions.
Users must enter a country name to obtain ISO Codes.
Each endpoint returns JSON data containing ISO codes for countries and subdivisions. For example, the "Get ISO codes by country" endpoint returns the country name along with its alpha-2, alpha-3, and numeric codes.
The key fields in the response data include "name" (country or subdivision name), "alpha2Code" (ISO 3166-1 alpha-2 code), "alpha3Code" (ISO 3166-1 alpha-3 code), and "numericCode" (ISO numeric code).
Each endpoint provides specific information: country names and their ISO codes, subdivisions by country, and the ability to retrieve data using different ISO code formats (2 or 3).
The response data is organized as an array of JSON objects. Each object contains fields like "name," "alpha2Code," "alpha3Code," and "numericCode," allowing for easy parsing and integration.
The data is sourced from the ISO 3166 standard, which is maintained by the International Organization for Standardization. This ensures that the codes are accurate and up-to-date.
Users can customize their requests by specifying parameters such as country names or ISO codes when calling the respective endpoints, allowing for targeted data retrieval.
Typical use cases include address validation for e-commerce, international shipping documentation, multilingual website localization, and academic research data organization.
Users can utilize the returned data by integrating it into applications for tasks like validating addresses, processing transactions, or displaying country information in user interfaces, enhancing functionality and user experience.
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.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the worldβs most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the βX-Zyla-API-Calls-Monthly-Remainingβ field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.
To see the maximum number of API requests your plan allows, check the βX-Zyla-RateLimit-Limitβ response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.
The βX-Zyla-RateLimit-Resetβ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, itβs important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.
Service Level:
100%
Response Time:
6,038ms
Service Level:
100%
Response Time:
570ms
Service Level:
100%
Response Time:
1,779ms
Service Level:
100%
Response Time:
1,551ms
Service Level:
100%
Response Time:
127ms
Service Level:
100%
Response Time:
86ms
Service Level:
100%
Response Time:
2,491ms
Service Level:
89%
Response Time:
979ms
Service Level:
100%
Response Time:
2,429ms
Service Level:
100%
Response Time:
514ms