The Pollen API lets you request pollen information including types, plants, and indexes for a specific location. The API provides endpoints that let you query:
Returns daily forecast pollen conditions for a specific location. Each daily forecast includes pollen index for types of plants for 1 to 5 days.
Note: We provide a 5-day pollen forecast for all plant types in Canada and the U.S. For other countries, we provide a 5-day pollen forecast for these plants:
For all other plants, we provide a 3-day pollen forecast.
While making an API request, certain parameters are mandatory, while others are optional.
This example shows a request to get the daily pollen conditions for central Paris
(48.857456, 2.354611) using the default request parameters settings.
In this example only some of the available data fields returns, as it uses the default settings, which sets only the types_information feature. You can expect "today" as the first object in the array, followed by two more object, each one for the following day. The days are based on the local time at the requested location.
The request returns this response:"loading..."
In the example, the request was customized to include additional features:
Both request made with default and customized settings are counted the same, regardless of the number of features included in the original query. With pollen daily forecast, each day is counted as one object. If you requested 3 days, they will be counted as 3 objects.
data field is an array, where each of the objects include the following fields:
You can customize any API request to only include the data you need for your software. This allows you to save bandwidth and decrease response time by requesting less information. You customize request data returned using the features parameter to define the feature or list of features to include in the response.
The following returns daily forecast pollen conditions including the types_information and plants_information features:
Unless you have specified the features parameter in the request, the response returns only the pollen types information.
Here are the various supported features and details on each of them.
weedfor each including their BreezoMeter Pollen Index, color, category and seasonality.
|Type||Tree, Weed, Grass|
|Family||Birch family, Olive Family, etc.|
|Pollen season||The period when pollen levels are high,|
e.x Late winter, early spring
|Special shapes||Shapes of leaves, bark, flowers or seeds|
that help identify the plant
|Special colors||Colors of leaves, bark, flowers or seeds|
that help identify the plant
|Cross reaction||People with allergy to a certain plant might|
also have a reaction with other specific plants
Any request to an API endpoint can return metadata that describes the original request. You request metadata by including the metadata parameter in your request with the value true. When excluding the metadata parameter, or setting it to false, the metadata field returns null.
When requested, it has a slightly different structure, depending on the request type.
Requests for the current day, or the next number of days return an array with a single object or multiple objects, and a metadata object with a range of dates. This example shows a request to the daily forecast endpoint for today that returns metadata:
The request’s JSON response includes the following metadata object:"loading..."
Metadata objects can include these fields.
The BreezoMeter Pollen API supports various plants, which are made accessible through the different pollen endpoints. Plants’ availability is subject to actual measurements and reports available for BreezoMeter to use, and is changing between different locations.
Here are the various plants’ codes and their metadata we might return: