ApivomApivom
Get Demo

Google Air Quality API Connector

Google's Air Quality API — current conditions, hourly forecasts and history with universal and local AQI indexes, pollutant concentrations and health recommendations for any coordinate, plus heat-map tiles — registered in Apivom Atlas for environment, health and facilities tenants, with your own Maps Platform key.

What you can do

  • Current conditions: Universal AQI plus the local index of the country, dominant pollutant and health recommendations by population group
  • Hourly forecast up to 96 hours ahead and history up to 30 days back for a coordinate
  • Pollutant concentrations (PM2.5, PM10, O₃, NO₂, SO₂, CO) and additional info on sources and effects
  • Heat-map tiles for rendering AQI layers on a map; four routes, one read-only

Use cases

  • Protect outdoor crews — Check the hourly AQI forecast for a site before scheduling outdoor work and reschedule when the index for sensitive groups is poor.
  • Air-quality context on locations — Show current and historical AQI for the sites, branches or properties you manage, with the dominant pollutant and recommendations.

The Air Quality API on airquality.googleapis.com is one of Google Maps Platform's environment services. For any latitude and longitude it returns current air quality — the Universal AQI and, where available, the country's own index, the dominant pollutant, pollutant concentrations and health recommendations for the general population and sensitive groups — as well as an hourly forecast up to four days ahead and hourly history up to a month back. A fourth route serves heat-map tiles so an AQI layer can be drawn over a map. Apivom Atlas registers all four routes with the Maps Platform credential contract, per-tenant logging and the AI integration guide (llms.txt); your key, project and quotas apply. No Apivom product workflow consumes air-quality data today — the connector is available to tenants who build facilities, health or outdoor-operations features on it, and a product flow is scoped per customer.

Authentication

Your own Google Cloud API key (Maps Platform) with this API enabled on the project; the Apivom product sends it as the x-goog-api-key header on each call. Google bills the project that owns the key. The key is encrypted in your Iris tenant; Apivom Atlas stores nothing.

Frequently asked questions

Can I switch this connector on today?

The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.

Which indexes are reported?

Always the Universal AQI (0–100, higher is better) and, when you request extra computations, the local index used in that country (for example the European EAQI or the US EPA AQI), together with pollutant concentrations and health recommendations.

Which Google Cloud project pays for the calls?

The project that owns the API key you connect. Enable this specific API on that project, restrict the key to the APIs you actually use, and Google's Maps Platform pricing and monthly credit apply to it directly — Apivom adds no charge and shows every call in your tenant's integration log.

Does Apivom charge per API call for this connector?

No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.

Where are my credentials stored and who can see the traffic?

Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.

More Atlas integrations

AI integration guide (llms.txt)

Machine-readable markdown — feed it to your AI assistant as integration instructions.