The City Life Quality API enables developers and data consumers to query real-time quality of life rankings and statistics for global cities as provided by Numbeo. Instead of retrieving the entire dataset at once, this API is segmented into targeted endpoints that expose each quality metric individually. Users can retrieve the list of cities globally and then access specific metrics for cities within a particular country using simple RESTful queries. This modular design enhances performance, minimizes payload size, and supports scalable data analytics across domains like urban planning, travel, and HR benchmarking.
{"countries":["Netherlands","Luxembourg","Switzerland","Denmark","Spain","Finland","Norway","Austria","Germany","Australia","United Kingdom","Oman","New Zealand","United States","Iceland","Canada","Portugal","Czech Republic","France","Brazil","Italy","South Africa","United Arab Emirates","Lithuania","Estonia","Ireland","Romania","Turkey","India","Mexico","Argentina","Japan","Russia","Vietnam","Pakistan","Colombia","Philippines","Bangladesh","Greece","Bulgaria","Serbia","Kazakhstan","Malaysia","Chile","Ukraine","Singapore","Hong Kong","Czech Republic","Namibia","Algeria","Saudi Arabia","Kuwait","Taiwan","Costa Rica","Panama","Guatemala","Dominican Republic","Morocco","Nepal","Egypt","Sri Lanka","Iran","Nigeria"]}
curl --location --request POST 'https://zylalabs.com/api/6584/city+life+quality+api/9624/obtain+countries+listing' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
{"country":"Argentina","cities":["Buenos Aires"]}
curl --location --request POST 'https://zylalabs.com/api/6584/city+life+quality+api/9625/acquire+cities+by+country' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"country":"Required"}'
{"city":"Buenos Aires, Argentina","purchasing_power":45.9}
curl --location --request POST 'https://zylalabs.com/api/6584/city+life+quality+api/9626/get+purchasing+power+by+city' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"city":"Required"}'
{"city":"Buenos Aires, Argentina","safety_index":36.9}
curl --location --request POST 'https://zylalabs.com/api/6584/city+life+quality+api/9627/get+safety+index+by+city' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"city":"Required"}'
{"city":"Buenos Aires, Argentina","health_care_index":36.9}
curl --location --request POST 'https://zylalabs.com/api/6584/city+life+quality+api/9628/get+healthcare+index+by+city' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"city":"Required"}'
{"city":"Buenos Aires, Argentina","quality_of_life":116.6}
curl --location --request POST 'https://zylalabs.com/api/6584/city+life+quality+api/9629/get+quality+of+life+index' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"city":"Required"}'
| 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 City Life Quality API provides structured access to data about quality of life metrics in cities worldwide, including indicators such as purchasing power, safety, healthcare, climate, and traffic.
You can access specific quality of life metrics for a city by using the API's targeted endpoints, which allow you to query individual metrics for cities within a particular country using simple RESTful queries.
The API provides various quality of life indicators, including purchasing power, safety, healthcare, climate, and traffic, allowing users to analyze different aspects of urban living.
Yes, the API allows users to filter data by country, enabling you to retrieve quality of life metrics for cities specifically within the selected country.
The modular design of the API enhances performance by allowing users to retrieve only the necessary data through targeted endpoints, minimizing payload size and supporting scalable data analytics.
Each endpoint returns specific quality of life metrics for cities. For example, the "get purchasing power by city" endpoint returns the Purchasing Power Index, while the "get safety index by city" provides the Safety Index. Each response includes the city name and the corresponding metric value.
The key fields in the response data typically include "city" (the name of the city), and the specific metric being queried, such as "purchasing_power," "safety_index," or "health_care_index," along with their respective values.
The response data is organized in a JSON format, where each response contains a city field and the corresponding metric value. For example, a response from the "get healthcare index by city" endpoint would look like: {"city":"Buenos Aires, Argentina","health_care_index":36.9}.
Each endpoint provides distinct information: the countries endpoint lists all countries, the cities endpoint lists cities by country, and the metrics endpoints provide specific indices like purchasing power, safety, healthcare, and overall quality of life for individual cities.
The primary parameters include "country" for the cities endpoint and "city" for the metrics endpoints. Users must specify these parameters to retrieve relevant data, such as cities in a specific country or metrics for a particular city.
Users can utilize the returned data by integrating it into applications for urban planning, travel analysis, or HR benchmarking. For instance, comparing purchasing power across cities can help businesses make informed relocation decisions.
The data is sourced from Numbeo, which aggregates user-contributed data on quality of life metrics. This ensures a broad and diverse dataset reflecting real-world conditions in various cities.
Typical use cases include urban planning, travel decision-making, and HR benchmarking. For example, companies can use the quality of life index to assess potential locations for new offices based on employee well-being and safety.
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:
4,338ms
Service Level:
100%
Response Time:
315ms
Service Level:
100%
Response Time:
845ms
Service Level:
100%
Response Time:
2,558ms
Service Level:
100%
Response Time:
74ms
Service Level:
100%
Response Time:
17,246ms
Service Level:
100%
Response Time:
368ms
Service Level:
100%
Response Time:
53ms
Service Level:
100%
Response Time:
1,067ms
Service Level:
100%
Response Time:
14,475ms
Service Level:
100%
Response Time:
2,201ms
Service Level:
100%
Response Time:
716ms
Service Level:
100%
Response Time:
280ms
Service Level:
100%
Response Time:
324ms
Service Level:
100%
Response Time:
301ms
Service Level:
100%
Response Time:
580ms
Service Level:
100%
Response Time:
1,377ms
Service Level:
100%
Response Time:
1,996ms
Service Level:
100%
Response Time:
111ms
Service Level:
100%
Response Time:
170ms