AQICN logo

AQICN

AQICN

UpFreeweather

Air Quality Index Data for over 1000 cities.

Visit site ↗Health checked 1d ago
Use it when

Covers over 1000 cities worldwide

Watch for

Check the docs depth and real endpoint shape before assuming production fit.

First check

Sign up to obtain an API key. Use the key to authenticate requests to access air quality data.

Auth
api_key
CORS
No
HTTPS
Yes
Signup
Required
Latency
914 ms
Protocol
REST
Pricing
free

Uptime · 30-day window

Probes: 30Uptime: 100%Avg latency: 819ms
01

About this API

The AQICN API provides access to air quality index data for over 1000 cities worldwide. It is designed for developers who need reliable and standardized air pollution information to integrate into their applications or services.

This API is relevant for weather apps, environmental monitoring tools, and public health platforms that require up-to-date air quality metrics. By offering data across many locations, it enables broad geographic coverage for users interested in air pollution levels.

Authentication is handled via an API key, ensuring controlled access to the data. The API focuses on delivering essential air quality index values without additional unrelated features, making it straightforward for developers to incorporate environmental data into their projects.

02

What you can build

  • 1Display real-time air quality index for cities
  • 2Generate air pollution alerts based on AQI data
  • 3Integrate air quality data into weather applications
  • 4Visualize historical air quality trends
03

Strengths & limitations

Strengths

  • Covers over 1000 cities worldwide
  • Provides standardized air quality index data
  • Supports API key authentication
04

Getting started

Sign up to obtain an API key. Use the key to authenticate requests to access air quality data.

05

FAQ

Do I need an API key to use AQICN?+

Yes, an API key is required to authenticate and access the data.

What kind of data does the API provide?+

It provides air quality index data for over 1000 cities worldwide.

Is HTTPS required to access the API?+

While not explicitly stated, using HTTPS is recommended for secure communication.

Can I use the API directly from a browser?+

Usage from browsers depends on CORS policy, which is not specified here.

06

Technical details

CORS: NoHTTPS: YesSignup: YesOpen source: No
Auth type
api_key
Pricing
free
Protocols
REST
Response time
914 ms
Last health check
7/14/2026, 5:45:47 AM
07

Tags