BreezoMeter (now part of Google) is an environmental intelligence platform that delivers hyperlocal, real-time and forecast data on air quality, pollen, weather, and active wildfires. The BreezoMeter REST API aggregates readings from tens of thousands of government and commercial sensors, satellite observations, traffic patterns, and meteorological models to expose endpoints for current conditions, hourly and daily forecasts, historical data, heatmap tiles, cleanest-route insights, and area-based wildfire monitoring.
Power end-to-end data operations for your Breezometer API with Nexla. Our bi-directional Breezometer connector is purpose-built for Breezometer, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Breezometer or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Breezometer workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
The Breezometer API authenticates requests using an API key issued from the BreezoMeter developer dashboard. The key is included as a key query parameter on every request and identifies the account associated with the call for quota management, billing, and feature entitlements. Review the steps below to generate or retrieve the API key required to create a Breezometer credential in Nexla.
BreezoMeter and Google Maps Platform
BreezoMeter was acquired by Google in 2022, and several of its environmental data products have been folded into the Google Maps Platform (Air Quality API, Pollen API, Solar API). The legacy api.breezometer.com endpoints — which this connector targets — continue to be available to existing BreezoMeter customers under their existing keys. New customers building environmental data integrations should also evaluate the Google Maps Platform Air Quality API and Pollen API.
Sign in to the BreezoMeter Developer Dashboard at developers.breezometer.com/dashboard using the email associated with your BreezoMeter account.
From the dashboard, click the API Keys link in the side navigation to open the API key management page.
Click Create API Key (or Generate New Key), enter a descriptive name for the key (for example, nexla-integration), and confirm. The dashboard displays the newly generated key value immediately after creation.
Copy the API key value and store it in a secure secret manager. The key grants access to the products your BreezoMeter plan enables (Air Quality, Pollen, Weather, Wildfire Tracker+, Tiles, Insights), so it should be treated like a password.
Each Breezometer endpoint is gated by the products enabled on your plan. If a request returns a permissions error, confirm in the developer dashboard that the relevant product (for example, Wildfire Tracker+ for the area-monitoring endpoints, or Tiles for the heatmap endpoints) is enabled for the API key being used.
The API key grants access to BreezoMeter API quota and data tied to your account. Store it in a secure secret manager, never commit it to source control, and rotate the key immediately if you suspect it has been exposed.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter the API key generated from the BreezoMeter Developer Dashboard in the API Key Value field. Nexla stores this value as an encrypted secret and automatically appends it as the key URL parameter on every Breezometer API request.
The Breezometer connector includes a built-in connection test that calls GET https://api.breezometer.com/air-quality/v2/current-conditions?lat=48.857456&lon=2.354611 with the supplied key to verify the credential is valid. If the test fails, confirm that the key has not been revoked and that the Air Quality product is enabled for the key in the BreezoMeter dashboard.
Click the Save button at the bottom of the overlay to save the configured credential. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Breezometer connector tile, then select the credential that will be used to connect to the Breezometer instance, and click Next; or, create a new Breezometer credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Breezometer endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.
Air Quality - Current Conditions
This endpoint returns the current air-quality conditions for a single geographic point — including the BreezoMeter AQI, dominant pollutant, pollutant concentrations, and health recommendations. It also supports point-in-time and range queries against the recent historical window when the relevant datetime parameters are supplied.
Enter the geographic latitude in the Latitude field (decimal degrees, for example 48.857456) and the longitude in the Longitude field (for example 2.354611). These two values are the minimum required inputs.
To request data for a single past moment, enter an ISO 8601 timestamp in the Datetime field (for example 2026-05-15T14:00:00Z). Leave this field blank to return the latest available conditions.
To request a historical range, leave Datetime blank and enter ISO 8601 values in both Start Datetime and End Datetime. The endpoint returns one record per hour within the requested window.
To extend the response payload, enter a comma-separated list of feature names in the Features field. Supported values include breezometer_aqi, local_aqi, health_recommendations, sources_and_attribution, pollutants_concentrations, and dominant_pollutant_concentrations.
Set the Metadata field to true to include calculation timestamps and data-source attribution alongside each reading.
Enter a language code in the Language field (for example en, es, fr) to localize human-readable text such as health recommendations.
Set the BreezoMeter AQI Color field to true to include the AQI category color codes used by BreezoMeter visualizations.
This endpoint returns the air-quality forecast for a specific future hour at the requested location. Use it to surface a single forecast slot — for example, to populate "tomorrow at 09:00 AQI" in a downstream system without retrieving the entire forecast window.
Enter the location coordinates in the Lat and Lon fields. Both are required.
Enter the target forecast time in the Datetime field as an ISO 8601 timestamp (for example 2026-06-02T09:00:00Z). This is required and must fall within BreezoMeter's forecast window (typically up to 96 hours into the future).
Optionally, enter a comma-separated list of feature names in the Features field to extend the response (for example local_aqi,health_recommendations,pollutants_concentrations).
Set the Metadata field to true to include calculation timestamps and source attribution.
Enter a language code in the Lang field to localize human-readable text.
Air Quality - Hourly History (Specific Datetime)
This endpoint returns the historical air-quality reading for a specific past hour at the requested location. Use it to backfill a single past moment in a time series — for example, when reconciling sensor data against BreezoMeter readings for a fixed timestamp.
Enter the location coordinates in the Lat and Lon fields.
Enter the historical timestamp to look up in the Datetime field as an ISO 8601 value. This must fall within the historical window allowed by your BreezoMeter plan.
Optionally, enter a comma-separated list of feature names in the Features field to extend the response payload.
Set the Metadata field to true to include data-source attribution and timestamps.
Enter a language code in the Lang field to localize human-readable text.
To ingest a continuous historical range rather than a single point, use the Air Quality - Current Conditions endpoint with both Start Datetime and End Datetime populated.
Get BreezoMeter AQI Heatmap Tile
This endpoint returns a PNG heatmap tile visualizing current BreezoMeter AQI values for the requested map tile coordinates. Use it to overlay air-quality heatmaps on Mapbox, Leaflet, or Google Maps clients, or to archive geographic snapshots for later analysis.
Enter the slippy-map zoom level in the Zoom Level field (an integer between 0 and 21; lower values cover larger areas at lower resolution).
Enter the tile X and Y coordinates in the Tile X Coordinate and Tile Y Coordinate fields. These are standard XYZ tile coordinates and can be derived from a latitude/longitude pair using a tile-coordinate utility.
Enter the visualization color scheme in the Color Scheme field. The default BreezoMeter palette is used when this field is blank.
The response is a binary PNG image, not a JSON record. Nexla treats each tile as a binary payload — downstream destinations should be configured to write the response as a file rather than as parsed records. For tile details, see the BreezoMeter Tiles API documentation.
Monitor Active Wildfires in Area of Interest
This endpoint returns active wildfire data for the pre-defined Areas of Interest (AoIs) registered against your Wildfire Tracker+ subscription. Use it to drive alerting, dashboards, or downstream automation that reacts to active fires inside a managed footprint (for example, an insurer's covered properties or a utility's service territory).
Optionally, enter a comma-separated list of feature names in the Features field to extend the response with additional attributes such as perimeter geometry or smoke plume data.
Enter the desired distance/area unit system in the Units field (for example metric or imperial) to control the units used in the response.
Areas of Interest must be defined in advance by BreezoMeter against your API key. This endpoint does not accept ad-hoc coordinates — use the Wildfire Locate and Track endpoint to query around a specific lat/lon. For details, see the BreezoMeter Wildfire Tracker+ API documentation.
Get Burnt Area Monitoring Data
This endpoint returns burnt-area monitoring data for the pre-defined Areas of Interest (AoIs) registered against your Wildfire Tracker+ subscription. Use it to track damage extents after fire activity has subsided — for example, to feed loss-modeling pipelines or environmental impact reporting.
Enter the desired distance/area unit system in the Units field (for example metric or imperial) to control the units used in the response.
Like the active-fire variant, this endpoint operates against AoIs registered with BreezoMeter — it does not accept ad-hoc coordinates. Use Wildfire Burnt Area for point-and-radius queries.
Get PM2.5 Heatmap Tile
This endpoint returns a PNG heatmap tile visualizing current PM2.5 (fine particulate matter) concentrations for the requested map tile coordinates. Use it when you need a pollutant-specific overlay rather than the composite BreezoMeter AQI tile.
Enter the slippy-map zoom level in the Zoom Level field (an integer between 0 and 21).
Enter the tile X and Y coordinates in the Tile X Coordinate and Tile Y Coordinate fields. These are standard XYZ tile coordinates.
The response is a binary PNG, not JSON. Downstream destinations should be configured to write the response as a file.
Pollen - Daily Forecast
This endpoint returns daily forecast pollen conditions for a specific location for 1 to 5 days ahead, including pollen index values for tree, grass, and weed pollen types. Use it to feed pollen-aware health and wellness applications, advertising targeting, or environmental alerting.
Enter the location coordinates in the Lat and Lon fields.
Enter the number of forecast days to return in the Days field (an integer between 1 and 5).
Optionally, enter a comma-separated list of feature names in the Features field to extend the response — for example types_information for per-plant-type metadata, or plants_information for plant-level breakdowns.
Set the Metadata field to true to include calculation timestamps and source attribution.
Enter a language code in the Lang field to localize human-readable text.
This endpoint returns a PNG heatmap tile visualizing daily pollen forecast intensity for the requested map tile coordinates. Use it to overlay pollen heatmaps on map clients or to archive snapshots for time-series visualization.
Enter the slippy-map zoom level in the Zoom Level field (an integer between 0 and 21).
Enter the tile X and Y coordinates in the Tile X Coordinate and Tile Y Coordinate fields.
This endpoint returns a vector tile (PBF — Mapbox vector format) visualizing current traffic-induced air pollution for the requested map tile coordinates. Use it when you need to render street-level pollution as a styleable vector layer rather than a raster overlay.
Enter the slippy-map zoom level in the Zoom Level field. This parameter is required.
Enter the tile X and Y coordinates in the Tile X Coordinate and Tile Y Coordinate fields. Both are required.
The response is a binary Mapbox vector tile (.pbf). Configure downstream destinations to write the response as a binary file, and use a Mapbox-compatible client to render the styled layer.
Weather - Current Conditions
This endpoint returns the current weather conditions — temperature, apparent temperature, wind speed and direction, humidity, precipitation, and weather code — for a specific location. Use it as a companion to the air-quality and pollen endpoints to enrich environmental records with meteorological context.
Enter the location coordinates in the Latitude and Longitude fields. Both are required.
Set the Metadata field to true to include calculation timestamps and source attribution in the response.
Enter the unit system in the Units field (metric for Celsius/kph, imperial for Fahrenheit/mph).
Enter a language code in the Language field to localize human-readable text such as weather descriptions.
This endpoint returns daily weather forecast conditions for a specific location for up to five days ahead, including high/low temperatures, precipitation probability, and dominant weather conditions.
Enter the location coordinates in the Lat and Lon fields.
Enter the number of forecast days to return in the Days field (an integer between 1 and 5).
Set the Metadata field to true to include calculation timestamps and source attribution.
Enter the unit system in the Units field (metric or imperial).
Enter a language code in the Lang field to localize human-readable text.
Get Hourly Weather Forecast
This endpoint returns hourly weather forecast conditions for a specific location for up to 120 hours (five days) ahead. Use it for short-horizon planning workloads that need higher temporal resolution than the daily forecast.
Enter the location coordinates in the Latitude and Longitude fields.
Enter the number of forecast hours to return in the Number of Hours field (an integer up to 120).
Set the Include Metadata field to true to include calculation timestamps and source attribution.
Enter the unit system in the Units field (metric or imperial).
Enter a language code in the Language field to localize human-readable text.
This endpoint returns burnt-area data for a specific location within a given radius and lookback window after fire extinguishment. Use it for ad-hoc, point-and-radius damage assessments — for example, to evaluate fire impact around a specific address.
Enter the location coordinates in the Lat and Lon fields.
Enter the search radius in the Radius field (numeric, in the units specified by the Units field).
Enter the lookback window in the Daysfromextinguish field — the number of days since fire extinguishment to include in the result set.
Enter the desired unit system in the Units field (metric or imperial).
Wildfire Locate and Track
This endpoint returns active wildfire conditions and perimeter data for a specific location within a given radius. Use it for ad-hoc wildfire situational awareness around a specific point — for example, to enrich an alert with a list of fires currently burning within 50 km of an asset.
Enter the location coordinates in the Latitude and Longitude fields.
Enter the search radius in the Radius field (numeric, in the units specified by the Units field).
Enter the desired unit system in the Units field (metric or imperial).
Optionally, enter a comma-separated list of feature names in the Features field to extend the response with additional attributes such as fire perimeter geometry.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Breezometer data sources can also be manually configured to ingest data from any valid Breezometer API endpoint not covered by the pre-built templates — for example, the Environmental Alerts Insights Engine, custom feature combinations, specialized Tiles endpoints, or sources that chain calls across the Air Quality, Pollen, and Weather APIs to assemble a unified environmental record for a location. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
All Breezometer API URLs are rooted at https://api.breezometer.com/ followed by the product path (for example, https://api.breezometer.com/air-quality/v2/current-conditions or https://api.breezometer.com/pollen/v2/forecast/daily). The credential automatically appends the API key as the key URL parameter, so no Authorization header is required.
Most JSON endpoints wrap the payload in a top-level data object: set the path to data to $.data for point queries that return a single object, $.data[*] for endpoints that return an array, and $ for tile endpoints that return a binary PNG or vector payload. Capture the metadata sibling at $.metadata to retain calculation timestamps and source attribution. For datetime, start_datetime, and end_datetime macros, use an ISO 8601 date format such as yyyy-MM-dd'T'HH:mm:ssXXX.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Breezometer data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Breezometer destination, and select the Send to Destination option from the menu. Select the Breezometer connector from the list of available destination connectors, then select the credential that will be used to connect to the Breezometer account, and click Next; or, create a new Breezometer credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to Breezometer Insights endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Calculate Cleanest Route
This endpoint posts one or more candidate routes (each a sequence of geographic points) to the BreezoMeter Insights Engine and returns a cleanliness score (0–100) for each route based on the air quality the route is exposed to. Use it to power health-aware routing — for example, surfacing the lowest-pollution walking, cycling, or driving option in a mobility application.
The full record is sent as the JSON body of POST /insights/v1/cleanest-route. Use the Nexla transform layer to shape each upstream record into the request payload expected by BreezoMeter, including the list of candidate routes and the points that define each route.
Each route should consist of an ordered list of lat/lon points along the path. Routes that share start and end points but differ in geometry can be compared against each other directly.
The response includes a cleanliness score for each submitted route along with summary air-quality statistics across the route geometry.
This endpoint submits a batch of monitored user locations to the BreezoMeter Environmental Alerts Insights Engine. The Insights Engine evaluates current and forecast environmental conditions (air quality, pollen, weather, wildfires) against each location and asynchronously returns alert notifications to a webhook URL registered against your BreezoMeter account.
The full record is sent as the JSON body of POST /insights/v1/environmental-alerts. Use the Nexla transform layer to shape each upstream record into the request payload expected by BreezoMeter — typically a list of user identifiers, their locations, and the alert categories they have subscribed to.
Alert notifications are not returned in the synchronous response — they are pushed to the webhook URL configured for your BreezoMeter account. The synchronous response acknowledges that the submission was accepted for processing.
Before activating this destination, confirm that an Environmental Alerts webhook URL is configured for your BreezoMeter API key. For details on the webhook payload format and the supported alert categories, see the BreezoMeter Environmental Alerts API documentation.
Breezometer destinations can also be manually configured to send data to any valid Breezometer API endpoint not covered by the pre-built templates or when custom payload shaping is required. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
Breezometer Insights destinations use the POST method with a JSON request body. Insights URLs are rooted at https://api.breezometer.com/insights/v1/ (for example, https://api.breezometer.com/insights/v1/cleanest-route or https://api.breezometer.com/insights/v1/environmental-alerts). The credential automatically appends the API key as the key URL parameter, and the Content-Type: application/json header is set automatically. Batching multiple monitored users into a single Environmental Alerts request can reduce overhead and help stay within rate limits. Enable Would you like to process the API response as a Nexla Webhook source? to capture Breezometer responses — such as Cleanest Route cleanliness scores — into a downstream Nexset.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to the configured Breezometer endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to Breezometer until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
