Error: "You must supply a key"

  • 17
  • Problem
  • Updated 5 years ago
We have just signed up after initial webserver problems this morning. We have created one key and are receiving the 'you must supply a key' error to all attempts to use your API.

"error": {
"type": "missingkey"
,"description": "you must supply a key"
}

We have also tried regenerating the key just in case there was some database issue as when we signed up your website was offline and reporting errors throughout the sign up process.

Please advise.
Photo of ObjectLabs

ObjectLabs

  • 1 Post
  • 0 Reply Likes
  • frustrated

Posted 6 years ago

  • 17
Photo of EIZSOFT

EIZSOFT

  • 17 Posts
  • 0 Reply Likes
same here urgent !!!!!!!!!!!!!!!!!!
Photo of whateverworks2012

whateverworks2012

  • 5 Posts
  • 0 Reply Likes
Same Here!
response = {
error = {
description = "you must supply a key";
type = missingkey;
};
features = {
};
termsofService = "http://www.wunderground.com/weather/a...";
version = "0.1";
};
}
Photo of esltoday

esltoday

  • 2 Posts
  • 0 Reply Likes
Same issue here!!
Photo of Peebuste

Peebuste

  • 1 Post
  • 0 Reply Likes
Good thing is, now I know to avoid WU for more serious application
Photo of reinstoss

reinstoss

  • 4 Posts
  • 0 Reply Likes
Same issue here!! I need a fix!
Photo of ip00

ip00

  • 2 Posts
  • 0 Reply Likes
Same here, something is broken.

{
"response": {
"version": "0.1"
,"termsofService": "http://www.wunderground.com/weather/a..."
,"features": {
}
,
"error": {
"type": "missingkey"
,"description": "you must supply a key"
}
}
}
Photo of DeltaSystems

DeltaSystems

  • 4 Posts
  • 0 Reply Likes
Same issue here. Can you fix this,please?
Photo of duckworth

duckworth

  • 2 Posts
  • 0 Reply Likes
+1 Same issue.
Photo of kbouwkamp

kbouwkamp

  • 1 Post
  • 0 Reply Likes
+1 my weather is broken!
Photo of Brendan Hayes

Brendan Hayes, Official Rep

  • 962 Posts
  • 123 Reply Likes
We are looking into this issue. I'm going to keep posting on this same thread: http://apicommunity.wunderground.com/...

Follow for updates there. Sorry for this problem! We're working to resolve it as fast as possible.
Photo of apilink

apilink

  • 1 Post
  • 0 Reply Likes
me too
Photo of ChronicStim

ChronicStim

  • 2 Posts
  • 0 Reply Likes
Seems to be back up now for us. Once the crisis is over, it would be nice to have an explanation of why the problem occurred and how we can mitigate it in the future should it happen again. Our customers blame us when these outages occur.
Photo of Brendan Hayes

Brendan Hayes, Official Rep

  • 962 Posts
  • 123 Reply Likes
This is fixed now. There was a problem with the API database replication where we lost the key table. Everything was backed up, everything was restored, and we're putting checks in place to catch this from happening again. Its the first time we've had a problem that wasn't trapped by checks before becoming an issue. We apologize for the inconvenience this has caused to everyone and we will be learning from this situation to provide better communication on the API pages.
Photo of ChronicStim

ChronicStim

  • 2 Posts
  • 0 Reply Likes
Thanks Brendan. The explanation is appreciated, as is the quick fix. This did raise a question for us that I'd like to get clarification on. If you guys decide to change either the request syntax or response content at some point, how much notice will you be giving subscribers so that we can update and distribute new versions of our apps?

We currently integrate your service in an iOS mobile app, so it generally takes a minimum of 7 days to get an update through the Apple review process and out to our users, so we need a good bit of lead time to make sure we can adapt to the change without service interruption for our users.

How will you make that notice - I'm assuming via our account emails, but just want to clarify?

And will this notice policy apply to users at the "Free" subscription level as well?

Thanks again.
Photo of Brendan Hayes

Brendan Hayes, Official Rep

  • 962 Posts
  • 123 Reply Likes
We're aware of how integrated the API is into apps, and the review period required for code changes and app stores submissions. We try and keep all of that in mind when making updates. When we update new data in the coming months, we'll be making new versions of the features on the URL. Right now we're looking at the idea of making /astronomyV2/ for example. We'll post here, on Twitter, and on the API stats pages when we'll be making changes, but the goal is that current users will not be affected until they decide to take advantage of the new features.
Photo of Nicholas Sosnicki

Nicholas Sosnicki

  • 1 Post
  • 0 Reply Likes
Beginning 3 days ago, I get this error when trying to pull down data using WeatherSnoop. I've tried a few different stations with the same result:

2013-08-31 12:38:08.150 Requesting data for KMASCITU6
2013-08-31 12:38:08.454 Received data for KMASCITU6
2013-08-31 12:38:08.456 0.1http://www.wunderground.com/weather/a... must supply a key

I've also opened a support case with WeatherSnoop (not sure exactly where the problem is).

Thanks.
Photo of joe smith

joe smith

  • 1 Post
  • 0 Reply Likes
I am having the same problem as above, when using WeatherSnoop to try and download weather data from a Wunderground station:

"Error: you must supply a key"