Whenever I try to interact with yahooapis, I get the following response:
<yahoo:error xmlns:yahoo="http://www.yahooapis.com/v1/base.rng" xml:lang="en-US" yahoo:uri="http://yahoo.com">
<yahoo:description> Please provide valid credentials. OAuth oauth_problem="OST_OAUTH_PARAMETER_ABSENT_ERROR", realm="yahooapis.com" </yahoo:description>
</yahoo:error>
This same response comes from the first link in the tutorial: <a href="http://weather.yahooapis.com/forecastrss?w=12797282">http://weather.yahooapis.com/forecastrss?w=12797282</a><a href="http://weather.yahooapis.com/forecastrss?w=12797282"></a>
as well as from
http://{org-name}-test.apigee.net/v1/weather/forecastrss?w=12797282 |
(with org-name replaced, of course)
Solved! Go to Solution.
@Timothy We have published a new proxy bundle. You can find it here: https://github.com/apigee/api-platform-samples/tree/master/default-proxies/helloworld
Please give it a try.
same problem here
,Same problem here please help !!
can you share the link of the tutorial you are reffering to?
http://docs.apigee.com/api-services/tutorials/part-1-create-your-api-xml
I believe Arghya Das is correct that Yahoo's weather api is no longer public.
@Timothy The problem is that the yahoo weather api that the sample proxy in the tutorial calls, is now changed. The target endpoint that we use is http://weather.yahooapis.com which seems to be expecting an oauth token now. This used to be open all this while. We would need to change the endpoints that we use in the same proxies to go to an alternate target endpoint that's open and accessible publicly.
please any proposition for target endpoint accessible publicly ?
You can try using http://httpbin.org/. It has a very rich set of features when it comes to mocking various kinds of responses. Please give it a try.
@Timothy I just looked through some blogs and it says as of yesterday, the yahoo weather api is no more a public API. It now requires an OAuth token to authenticate.
How can you confirm this ?
If you make an api call to the proxy you just mentioned, and open trace then you would see the 401 response coming from the yahoo weather api backend. It would be something like the screenshot I attached. I don't know if this is a temporary or permanent change from the yahoo weather api, but as soon as I find out more, I will let you know.
You can follow the blogpost here or checkout the Yahoo Weather API homepage (which also seems to have been changed recently). I will go ahead and log a request with our engineering team to remove the yahoo weather api endpoint from our sample proxies.
Thanks so much for finding this for me! I appreciate it very much.
hello
i want to use yahoo wheather api for my project i c# but now with out token not run you can have me an example? this service questions is free and service?
thank you
@Michele Benedetti I did not get you question. Are you saying you want to use the yahoo weather api in you project but without the oauth token ? The yahoo weather api has been deprecated by yahoo and the new one requires oauth. If you want just any other public api endpoint, you can use httpbin.org
@Timothy We have published a new proxy bundle. You can find it here: https://github.com/apigee/api-platform-samples/tree/master/default-proxies/helloworld
Please give it a try.