About the API:
Welcome to the Information By Cities API, your gateway to a treasure trove of data on cities worldwide. With a vast repository of statistics, this API delivers a comprehensive snapshot of tens of thousands of cities, empowering users with invaluable insights.
The API response format is user-friendly, presenting an array of information for each city. For example, unravel the mystique of Buenos Aires, discovering its geographical coordinates with latitude -34.5997 and longitude -58.3819. Gain an understanding of its national affiliation with the country code "AR," and delve into demographic nuances with a population count of 16,157,000. Notably, the boolean field "is_capital" reveals whether a city proudly serves as the capital.
Whether you're a developer crafting interactive maps, a researcher exploring urban demographics, or a traveler seeking city profiles, the Cities Information API caters to diverse needs. Seamlessly integrate this API to enhance your applications, infuse geographical intelligence into your projects, and unravel the stories embedded within the fabric of cities worldwide. Explore, analyze, and leverage the wealth of city data at your fingertips with the Cities Information API – transforming information into actionable insights.
The API provides useful statistics about tens of thousands of cities around the world.
Travel Planning Applications: Integrate the Cities Information API into travel planning apps to provide users with detailed city statistics. Travelers can explore key details such as population, geographic coordinates, and capital status, aiding them in making informed decisions about their destinations.
Real Estate Analysis: Developers creating real estate applications can leverage the API to offer insights into the cities where properties are located. By incorporating population data, geographical coordinates, and capital status, users can assess the desirability and growth potential of specific urban areas.
Educational Resources: Educational platforms can utilize the API to enrich geography lessons by providing students with real-world data about cities. Teachers and students can explore and compare cities globally, fostering a deeper understanding of demographics, geography, and cultural diversity.
Business Expansion Strategies: Businesses looking to expand their operations can use the API to analyze potential new locations. By considering population size, capital status, and geographical positioning, companies can make informed decisions on where to establish or expand their presence.
Smart City Development: Urban planners and government authorities can incorporate the Cities Information API into smart city initiatives. The API's data on cities facilitates informed decision-making for infrastructure development, resource allocation, and urban planning, contributing to the creation of more sustainable and efficient urban environments.
Besides the number of API calls per month, there is a limit of 20 requests per minute.
Get city data from either a name or population range. Returns a list of cities that satisfies the parameters.
Data - Endpoint Features
| Object | Description |
|---|---|
name |
[Required] name of city |
[{"name": "Houston", "latitude": 29.7863, "longitude": -95.3889, "country": "US", "population": 5464251, "is_capital": false}]
curl --location --request GET 'https://zylalabs.com/api/3430/information+by+cities+api/3733/data?name=houston' --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 commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The API response includes essential statistics such as the city's name, latitude, longitude, country code, population count, and a boolean flag indicating whether the city serves as the capital.
To access the API, you need to make HTTP requests to the designated endpoint. Authentication using API keys may be required, depending on the service provider's implementation.
The population data is typically sourced from the latest available statistics and may not be real-time. Users are encouraged to check for updates regularly or refer to the API documentation for data refresh intervals.
Yes, the API supports batch requests. You can provide a list of city names or IDs, and the API will return information for all specified cities in a single response.
The geographical coordinates (latitude and longitude) are sourced from reputable databases and are generally accurate. However, users should be aware that coordinates might represent a central point within a city.
The GET Data endpoint returns a list of cities based on specified parameters, including city name or population range. Each city entry includes details such as name, latitude, longitude, country code, population, and capital status.
The key fields in the response data include "name" (city name), "latitude" (geographical latitude), "longitude" (geographical longitude), "country" (country code), "population" (total residents), and "is_capital" (boolean indicating capital status).
The response data is structured as a JSON array, where each element represents a city object containing the aforementioned key fields. This format allows for easy parsing and integration into applications.
Users can customize their requests using parameters such as "city name" to search for specific cities or "population range" to filter cities based on their population size.
The GET Data endpoint provides geographical, demographic, and administrative information about cities, including their coordinates, population figures, and whether they are capitals, facilitating diverse applications.
The data is sourced from reputable databases and statistical agencies, ensuring a high level of accuracy and reliability. Continuous updates and quality checks help maintain data integrity.
Users can leverage the returned data for various applications, such as travel planning, real estate analysis, and educational resources, by integrating city statistics into their platforms for enhanced user experiences.
If the API returns partial or empty results, users should verify their input parameters for accuracy. Implementing error handling in the application can help manage such scenarios gracefully, providing fallback options or user notifications.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used 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.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
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, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
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.
Service Level:
100%
Response Time:
2,554ms
Service Level:
100%
Response Time:
368ms
Service Level:
100%
Response Time:
1,480ms
Service Level:
100%
Response Time:
544ms
Service Level:
100%
Response Time:
598ms
Service Level:
100%
Response Time:
479ms
Service Level:
100%
Response Time:
2,489ms
Service Level:
100%
Response Time:
513ms
Service Level:
100%
Response Time:
4,111ms
Service Level:
100%
Response Time:
544ms
Service Level:
100%
Response Time:
503ms
Service Level:
100%
Response Time:
381ms
Service Level:
100%
Response Time:
467ms
Service Level:
100%
Response Time:
79ms
Service Level:
100%
Response Time:
5,476ms
Service Level:
60%
Response Time:
2,150ms
Service Level:
100%
Response Time:
456ms
Service Level:
100%
Response Time:
1,017ms
Service Level:
100%
Response Time:
3,408ms
Service Level:
100%
Response Time:
110ms