that is the link that WD does you too
but not all browsers work very well with it
so try Edge maybe
It’s not very clear who actually needs to get the new API and why? Is this something a PWS owner who SENDS data to WU need to take action? Or as the subject points out, this is for people who run WD and PULL (stationless) data from WU?
Confused as usual here… :?
Also, I am unable to install build 92 here…tried downloading it twice and still won’t install giving me an error…“Windows cannot access the specified device, path, or file”
as per what the subject of this thread says
i.e only needed at this stage if you use WU as a data source for WD
but it will be needed for the 5 day forecast function in the almanac, but there does not seem to be any way to replace the almanac data (record hi/low for selected station) with the new api
edit, actually WD uses http://classic.wunderground.com/ to get the almanac data, so that should hopefully keep working
but the 5 day forecast and current conditions I will need to change to the new api and you will need to get and use your own api key
re your last statement, its not clear if you mean the full install or .zip update
Full install…haven’t tried the zip update…
I have tested and the full install works here
I do not have any other reports of a problem with it
maybe try a pc reboot?
actually WD used to use the classic url, for the almanac…but changed to using the api
but I can see if using the classic url will still work (it was not the best method as was just scraping the data from a web page)
done some experimenting
and
http://classic.wunderground.com/
does not exist anymore (moved permanently)
so RIP WU Almanac after the 22nd March 
I have moved the almanac and the wunderground station data (both via view )
to the new api
there is no record max/min available with the new api but you can use the manual data entry to set that so those custom tags work still
note that for the above 2 new screens, any station that was remembered has been reset and you need to get the new api key
also the search for stations is based on lat/long (geo code) and the latitude is a +ve value for west of GMT
the 5 day forecast works now from the new api (many hours spent getting that to work)
note that the old api is restricted for number of calls now and will close all together on the 22nd march
just a heads up
Good job, Brian 
the search for stations is based on lat/long (geo code) and the latitude is a +ve value for west of GMT
I had to put in a -ve value for longitude west of GMT :?
ops, I had that message backwards re longitude
Brian. Before all this new api stuff, I was using the WD/WU almanac successfully for years. I never had to get or purchase an api for this. Now, using 4 different browsers, the “get new api” link takes me only to my WU member settings page and nowhere is there an API function. What am I missing if you have a thought?
Thanks
the old WU api is going away
and there is no replacement for the almanac data
there is nothing I can do about that
re getting the new api key to use the 5 day forecast and conditions data from selected WU station ID
you get that via clicking on the link in WD
you might need to log out of WU and then log in again and you might need to use internet explorer browser
Brian:
The “Click here for link to API key” just takes me to my settings page. No api info at all there. I have logged out and in as well. Firefox, Edge, Chrome, Opera, IE
Thanks
it goes to
https://www.wunderground.com/member/api-keys
try logging out first and try using internet explorer
If you didn’t have an API key before, linked to a pws uploading to WU, I don’t think you can get a new API key?
oh, that is not very good if that is the case
I thought the requirement was just that you had to be a a PWS uploader/submitter
I might be wrong. . .
The requirement for a new key is you have a PWS uploading to WU … I don’t know if you had to have a prior WU API key.
Send a note to Victoria victoria.gardner at ibm.com and ask…
I think I am, here’s a direct quote from the forum: “Personal Weather Station (PWS) owners/contributors will continue to be eligible for a free replacement API service . . .”
(Unless “replacement API” implies “to replace your old one”.)
Ken’s right, try Victoria: [email protected]