The main purpose of a Geography Data API is to provide developers with a simple and efficient way to access geographic data from different sources and integrate it into their applications. This can be especially useful for applications that require location-based services such as mapping, geocoding, routing and geolocation.
One of the main advantages of using this API is that it eliminates the need for developers to create and manage their own geo-data databases. Instead, developers can access pre-existing datasets that are updated and maintained by the API provider. This can save time and resources and ensure that applications use the most accurate and up-to-date data.
Another advantage of using a Geography Data API is that it can provide developers with access to a wide range of geodata sets from different sources. This can include government data, private companies and other organizations. By providing access to multiple data sources, developers can create more complete and accurate applications.
One of the main features of this API is its ease of use. Most APIs provide simple, well-documented interfaces that developers can use to access geographic data. This can help speed up the development process and reduce the amount of code developers have to write.
Another important feature of a Geography Data API is its scalability. APIs are designed to handle large amounts of traffic and data requests, which means they can be used to power applications that have millions of users. This can be especially useful for applications that require real-time updates and data streams.
Overall, a Geography Data API can be an incredibly powerful tool for developers building location-based applications. By providing access to a wide range of geographic datasets and services, these APIs can help developers create more accurate, comprehensive and user-friendly applications.
It will receive parameters and provide you with a JSON.
Location-based marketing: Businesses can target their customers with location-based marketing campaigns and ads.
Logistics and supply chain management: The geo-data API can be used to optimize the accuracy of shipments.
Environmental monitoring: The geo-data API can be used to provide localization for applications that monitor environmental conditions, such as air quality, water quality and soil conditions.
Tourism and travel: The geo-data API can be used to provide information about different continents and countries.
Besides the number of API calls, there is no other limitation.
To use this endpoint all you have to do is insert an id between 1 and 6, to obtain continents.
Continent by Id - Endpoint Features
Object | Description |
---|---|
id |
[Required] |
{"id":1,"code":"AF","name":"Africa"}
curl --location --request GET 'https://zylalabs.com/api/1966/geography+data+api/1721/continent+by+id?id=1' --header 'Authorization: Bearer YOUR_API_KEY'
To use this endpoint all you have to do is insert in the parameters a page value, page size, and the name of a continent.
Continent by name - Endpoint Features
Object | Description |
---|---|
page |
[Required] |
pageSize |
[Required] |
name |
[Required] |
{"continents":[{"id":2,"code":"NA","name":"North America"}],"items":7,"numberOfPages":1,"currentPage":1}
curl --location --request GET 'https://zylalabs.com/api/1966/geography+data+api/1722/continent+by+name?page=1&pageSize=10&name=North America' --header 'Authorization: Bearer YOUR_API_KEY'
To use this endpoint all you have to do is insert in the parameter an id value.
Country by id - Endpoint Features
Object | Description |
---|---|
id |
[Required] |
{"id":10,"continentId":7,"code":"AR","name":"Argentina","native":"Argentina","phone":"54","capital":"Buenos Aires","currency":"ARS","emoji":"🇦🇷"}
curl --location --request GET 'https://zylalabs.com/api/1966/geography+data+api/1723/country+by+id?id=10' --header 'Authorization: Bearer YOUR_API_KEY'
To use this endpoint all you have to do is to insert in the parameter a value of page and page Size. These parameters are optional.
Countries by number - Endpoint Features
Object | Description |
---|---|
page |
[Optional] |
{"countries":[{"id":1,"continentId":6,"code":"AF","name":"Afghanistan","native":"افغانستان","phone":"93","capital":"Kabul","currency":"AFN","emoji":"🇦🇫"},{"id":2,"continentId":5,"code":"AL","name":"Albania","native":"Shqipëria","phone":"355","capital":"Tirana","currency":"ALL","emoji":"🇦🇱"},{"id":3,"continentId":1,"code":"DZ","name":"Algeria","native":"الجزائر","phone":"213","capital":"Algiers","currency":"DZD","emoji":"🇩🇿"},{"id":4,"continentId":3,"code":"AS","name":"American Samoa","native":"American Samoa","phone":"1684","capital":"Pago Pago","currency":"USD","emoji":"🇦🇸"},{"id":5,"continentId":5,"code":"AD","name":"Andorra","native":"Andorra","phone":"376","capital":"Andorra la Vella","currency":"EUR","emoji":"🇦🇩"},{"id":6,"continentId":1,"code":"AO","name":"Angola","native":"Angola","phone":"244","capital":"Luanda","currency":"AOA","emoji":"🇦🇴"},{"id":7,"continentId":2,"code":"AI","name":"Anguilla","native":"Anguilla","phone":"1264","capital":"The Valley","currency":"XCD","emoji":"🇦🇮"},{"id":8,"continentId":4,"code":"AQ","name":"Antarctica","native":"Antarctica","phone":"672","capital":"","currency":"","emoji":"🇦🇶"},{"id":9,"continentId":2,"code":"AG","name":"Antigua and Barbuda","native":"Antigua and Barbuda","phone":"1268","capital":"Saint John's","currency":"XCD","emoji":"🇦🇬"},{"id":10,"continentId":7,"code":"AR","name":"Argentina","native":"Argentina","phone":"54","capital":"Buenos Aires","currency":"ARS","emoji":"🇦🇷"}],"items":250,"numberOfPages":25,"currentPage":1}
curl --location --request GET 'https://zylalabs.com/api/1966/geography+data+api/1724/countries+by+number' --header 'Authorization: Bearer YOUR_API_KEY'
To use this endpoint all you have to do is insert in the parameter an id value.
Citys by id - Endpoint Features
Object | Description |
---|---|
id |
[Required] |
{"id":1,"location":{"latitude":27,"longitude":30,"locationType":"GeoPoint"},"cityId":"357994","name":"Arab Republic of Egypt","population":98423595,"adminCode":"00","countryId":"65"}
curl --location --request GET 'https://zylalabs.com/api/1966/geography+data+api/1725/citys+by+id?id=1' --header 'Authorization: Bearer YOUR_API_KEY'
To use this endpoint all you have to do is insert a value in page, page Size and the name of a city. These parameters are optional.
City by name - Endpoint Features
Object | Description |
---|
{"cities":[{"id":21,"location":{"latitude":-34.61315,"longitude":-58.37723,"locationType":"GeoPoint"},"cityId":"3435910","name":"Buenos Aires","population":13076300,"adminCode":"07","countryId":"10"}],"items":76597,"numberOfPages":76597,"currentPage":1}
curl --location --request GET 'https://zylalabs.com/api/1966/geography+data+api/1726/city+by+name' --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.
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, look at the ‘X-Zyla-API-Calls-Monthly-Remaining’ header. For example, if your plan allows 1000 requests per month and you've used 100, this header will show 900.
To see the maximum number of API requests your plan allows, check the ‘X-Zyla-RateLimit-Limit’ header. For instance, if your plan includes 1000 requests per month, this header will display 1000.
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 3600, it means 3600 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 let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.
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 trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.
Service Level:
89%
Response Time:
979ms
Service Level:
100%
Response Time:
866ms
Service Level:
100%
Response Time:
347ms
Service Level:
100%
Response Time:
396ms
Service Level:
100%
Response Time:
493ms
Service Level:
100%
Response Time:
849ms
Service Level:
89%
Response Time:
1,238ms
Service Level:
100%
Response Time:
1,551ms
Service Level:
100%
Response Time:
412ms
Service Level:
100%
Response Time:
1,163ms
Service Level:
100%
Response Time:
86ms
Service Level:
100%
Response Time:
429ms
Service Level:
100%
Response Time:
514ms
Service Level:
100%
Response Time:
75ms
Service Level:
100%
Response Time:
570ms
Service Level:
100%
Response Time:
652ms
Service Level:
100%
Response Time:
601ms