My current PurpleAir API-key which starts with “62F1F60C-C16B” is used by a decent number of users since we switched to using the API key some months ago.
PurpleAir mailed me today
Your PurpleAir API account has come up for review and we would like to turn on billing
Your PurpleAir API account will be migrated to the points-based billing system on October 31st
This email provides an opportunity to start a conversation with us about optimizing your points consumption prior to this change. In addition to a face-to-face meeting to discuss the details of this change and what options are available to you, more information about optimizing your points consumption can be found here: API Use Guidelines - API - PurpleAir Community.
As I do not know which users are using ‘my’ key "62F1F60C-C16B . . . " I can not warn them that at October 31 their PurpleAir scripts will cease to work
Please make sure that you request ASAP a correct key as described in this topic.
Make sure you test that key before October 31.
Also make sure that you, temporarily, insert your own key in the start-lines of PWS_load_files.php.
I have to adept the PWS_easyweathersetup (add PA-api-key) , PWS_settings (cache-time) and the PWS_load_files (remove PA-api-key) scripts to hide the new valuable API-key.
Adapted scripts posted in this topic .
After the scripts are updated and installed on your sites, I think it is wise to regenerate your purple-air API keys and insert the new keys using PWS_easyweathersetup.