Data interface / API
Recently, the (unofficial) data interface (API) of the Pollen+ app has increasingly appeared in third-party applications. Since this API was never designed for public use and the external calls put an additional load on the web server, we have decided to restrict the public use of this API.
Instead, we now offer an official API that provides the most important forecast data. This includes the pollen forecast data, as well as the allergy risk for today and the next three days.
Prerequisites for using this API:
- An API key, which is provided by us.
Please use this contact form or send an E-Mail to infohub(at)polleninformation.at and let us know what you would like to use the data interface for. We will then send you your personal API key. - If the data is used in publicly available applications, it is mandatory to name the origin of the data. (Austrian Pollen Information Service, www.polleninformation.at)
- The number of calls to the API is based on a fair-use basis so as not to overload the web server. We reserve the right to block access again in the event of disproportionately frequent calls. As the prediction data does not change continuously, a data retrieval every 4 hours is sufficient in most cases.
- The data from the API may not be used for commercial purposes.
- Calling the unofficial API of the Pollen+ app, starting with the URLs:
https://www.polleninformation.at/index.php?id=0&type=15976824 orhttps://www.polleninformation.at/index.php?eID=appinterface is no longer permitted.
Interface documentation
URL for retrieving the JSON data:
Parameter:
- twoLetterIsoCountryCode
The two-digit country code of the desired country (https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2)
Possible values: AT, CH, DE, ES, FR, GB, IT, LV, LT, PL, SE, TR, UA - twoLetterIsoLanguageCode
The two-digit language code for returning the titles of the allergens (https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes)
Possible values: de, en, fi, sv, fr, it, lv, lt, pl, pt, ru, sk, es, tr, uk, hu - latitude
The latitude of the desired position. e.g.: 48.20671631686089 - longitude
The longitude of the desired position. e.g.: 16.350157610474536 - apikey
The API key that we provide on request
JSON result:
{
contamination: [
{
poll_id: 23,
poll_title: "Pilzsporen (Alternaria)",
contamination_1: 3,
contamination_2: 3,
contamination_3: 3,
contamination_4: 3
},
{
poll_id: 5,
poll_title: "Gräser (Poaceae)",
contamination_1: 2,
contamination_2: 2,
contamination_3: 2,
contamination_4: 2
}
],
allergyrisk: {
allergyrisk_1: 8,
allergyrisk_2: 8,
allergyrisk_3: 8,
allergyrisk_4: 8
},
allergyrisk_hourly: {
allergyrisk_hourly_1: [
5,
5,
5,
5,
5,
4,
6,
8,
8,
8,
7,
6,
6,
4,
3,
3,
2,
1,
1,
1,
3,
3,
2,
2
],
allergyrisk_hourly_2: [
2,
2,
3,
3,
3,
3,
3,
4,
5,
7,
8,
8,
8,
8,
7,
6,
5,
6,
5,
4,
4,
4,
3,
3
],
allergyrisk_hourly_3: [
1,
1,
1,
1,
1,
1,
1,
1,
1,
1,
4,
4,
3,
5,
4,
5,
4,
2,
1,
1,
1,
1,
1,
0
],
allergyrisk_hourly_4: [
6,
6,
6,
6,
6,
6,
6,
5,
5,
5,
6,
7,
8,
7,
7,
7,
7,
7,
7,
7,
7,
7,
7,
7
]
}
}
contamination_1: Pollen load today from 0 (= no load) to 4 (= very high load)
contamination_2: Pollen load tomorrow from 0 to 4
etc.
allergyrisk_1: Allergy risk today from 0 (= no exposure) to 10 (= very high exposure)
allergyrisk_2: Allergy risk tomorrow from 0 to 10
etc.
allergyrisk_hourly_1: Hourly distribution of allergy risk today from 0 (= no exposure) to 10 (= very high exposure). (1st value = 12 a.m. to 1 a.m., 2nd value = 1 a.m. to 2 a.m., ...)
allergyrisk_hourly_2: Hourly distribution of allergy risk tomorrow from 0 to 10.
etc.
JSON result in case of error:
{
error: "invalid api key"
}