Release Notes
The AirQo API is regularly updated with new features, bug fixes, and performance improvements. You can specify which version of the API to load in the v parameter of the API request.
This changelog lists releases by date and version number, along with associated changes.
29th July 2022
- Added support for CSV responses with the introduction of a new query parameter (format)
- Responses are now in descending order with the most recent measurements at the top.
- Applied compression algorithms which have greatly decreased the size of the response body and hence increased the speed of the product.
- Addressed challenges with the datetime query parameters where the results were the start and end datetimes returned were not reflective of the exact query parameter values entered.
- Sanitised the timestamp output format, Initially, the timestamp returned as an object instead of just the string value.
7th October 2021
- Removed extra/unnecessary fields from events endpoint (s2_pm2_5 s2_pm10).
- The returned pollutant values (PM2.5 and PM10) is now the averages of the two sensors for each pollutant.
- Minimum frequency is now hourly , not raw values.
- Removes empty objects, arrays, empty strings, NaN, null and undefined values from response.
- Makes the query parameter recent=no as the default for the GET Events endpoint
7th October 2021
- Removed extra/unnecessary fields from events endpoint (s2_pm2_5 s2_pm10).
- The returned pollutant values (PM2.5 and PM10) is now the averages of the two sensors for each pollutant.
- Minimum frequency is now hourly , not raw values.
- Removes empty objects, arrays, empty strings, NaN, null and undefined values from response.
- Makes the query parameter recent=no as the default for the GET Events endpoint
24th September, 2021
- Remove extra/unnecessary fields (s2_pm2_5).
- The returned pollutant values are averages of the two sensors
- Minimum frequency of hourly , not raw values.
- Removes empty objects, arrays, empty strings, NaN, null and undefined values from response
- Added a new query parameter (external) whose default is always "yes".
- For the GET Events, one can now be able to retrieve hourly data using the frequency query parameter.
- Changed the
devicefield in the JSON response from_idtodevice.
- Added the
metadataquery parameter when fetching events. So a person can be able to select the type of metadata they want. Can either bedeviceorsite_idaccordingly.
Last modified 9mo ago