API-key not found after registration

  • 21
  • Problem
  • Updated 2 years ago
Today I signed up for a new api-key. Registration worked all fine (I can login now) but I cannot find a key anywhere on the site. An email with the requested key is also not received.
So after logging in, where do I find my api-key? Thank you in advance, Raymond.
Photo of EastNed

EastNed

  • 3 Posts
  • 1 Reply Like

Posted 5 years ago

  • 21
Photo of Tim Roche

Tim Roche, Official Rep

  • 309 Posts
  • 28 Reply Likes
To all in this thread,

We made some changes recently to the language on the site in hopes that that would help the situation.

If you do not have a wunderground account, you actually have to go through a 2 step process of registering.

You will have to create an account
receive an e-mail
log in (may have to do this 2x)
once you are logged in, you will be taken to a page that says "explore my options"
click that,
choose a plan
checkout
follow the checkout process

We realize this is not an Ideal process for signing up, and can cause confusion.

We are working on a new portal for the API, but as of yet, we have not seen a software problem in the signup process, but a UI flow problem.

If someone has gone through the process including filling out this page
http://www.wunderground.com/weather/a...

and not gotten a key, please e-mail tim@wunderground.com

Target date for the new portal to launch is next month, so hold tight and things should improve!

Apologies for the lack of responses to this thread, we are monitoring, and trying to improve your experience
Photo of newdad

newdad

  • 1 Post
  • 0 Reply Likes
Guys.. it failed in Chrome for me (got stuck in that same "loop" everyone was talking about). Fired up the old alternate browser test and tried the process from scratch with Firefox. It worked. Running Ubuntu 14.04 in my case... Whatever the latest versions are for Chrome and Firefox as of today. Thanks.

Thanks for this free service, Wunderground. Looking forward to testing out some projects.

Take care and God bless.
Photo of Tiziano Arbizzani

Tiziano Arbizzani

  • 2 Posts
  • 1 Reply Like
Dear Sirs,
I am experiencing a similar problem. I felt into the bug of "double registration need", but it was a non blocking bug, I just reapplied for a key (same data) and now my key is correctly showing in "Key Settings" along with all data I provided. But this key seems to be not correct. In "Documentation" page, if I try the example (Current Conditions in US City), clicking on "Show Response", the answer is shown, but if I copy+paste the link on my browser, I receive "keynotfound" error. And it's the same with other examples, too.
I tried with a second developer request (I thought the first was "burned" by registration bug...), but also second key is not functional.
Is there a time to wait to enable a key?
Thank you in advance.
Cheers,Tiziano.
Photo of Tim Roche

Tim Roche, Official Rep

  • 309 Posts
  • 28 Reply Likes
Thanks so much for the heads up! We had an issue with our database replication.  Your key should be working fine shortly.
Photo of Tiziano Arbizzani

Tiziano Arbizzani

  • 2 Posts
  • 1 Reply Like
Affirmative! Thank you very much!
Best regards,
T.
Photo of Josh Marshall

Josh Marshall

  • 2 Posts
  • 0 Reply Likes
I am having this problem too right now. The "Show Response" works but not if I copy and paste the link in another browser tab. Is there another db replication issue? Thanks in advance :)
Photo of Tom Batchelor

Tom Batchelor

  • 2 Posts
  • 0 Reply Likes
I just created my account about an hour ago, received my first key, and I'm having the same problem as Josh. Getting an error when I try to submit my own GETs: "this key does not exist". I tried regenerating my key once, then a second time, but still no luck.

Perhaps there's another hiccup in the system?
Photo of Josh Marshall

Josh Marshall

  • 2 Posts
  • 0 Reply Likes
Mine is working now. Must have been a slow replication. Tom maybe you can try yours again too
Photo of Tom Batchelor

Tom Batchelor

  • 2 Posts
  • 0 Reply Likes
Sure enough! It's working. I guess the lesson here is to wait 12 hours and try again before complaining on the forums! ;-)