|Yahoo! API - for web, news, image etc.|
Is this new? Experiences?
I just saw this: [developer.yahoo.net...] - FAQ here [developer.yahoo.net]
It's just like the Google API it seems. Anybody played with it yet? Experiences?
Hmm... Now this is news! Good catch claus!
I've been over it all day (local time, it's evening now) while waiting for this post to go through premoderation.
5000 queries per day - 5 times that of Google (per IP, not per ID), and you don't have to do the SOAP thing either. Great move Y!
(I found this related post [webmasterworld.com] from september as well.)
They've made it quite easy to get started. And free!
... and you can return 50 results, not just 10 as with Google
I had some trouble with the php example as i booted to windows this morning, but uncommenting this line in "php.ini" did the trick:
Now i've started looking at the Perl module [search.cpan.org] - that one seems quite rigorous :) Tip: Installing is as easy as typing this on the command line:
perl -MCPAN -e 'install Yahoo::Search'
I can see some 'made for Adsense' sites being created off the back of this one .... or may be even 'made for Yahoo's Competitor for Adsense' sites ;)
Nice one Y!
>I can see some 'made for Adsense' sites being created off the back of this one
Can't say I'm happy about the idea that this API will encourage more made-for-adsense sites however Y! is easy to scrape. I don't have monitoring tools that scrape Y! and report ranking results because that would be unauthorized use...but if I did, I would not rewrite them to use this API. Google is hard to scrape so it makes sense that they could be critisized for releasing an API. But anywho, I'm happy to see Y! catching up to Google and leveling the playing field a bit more.
Awesome! No more scraping :)
That's great. I was hoping that would happen:
|Can't say I'm happy about the idea that this API will encourage more made-for-adsense sites however Y! is easy to scrape. I don't have monitoring tools that scrape Y! and report ranking results because that would be unauthorized use...but if I did, I would not rewrite them to use this API. Google is hard to scrape so it makes sense that they could be critisized for releasing an API. But anywho, I'm happy to see Y! catching up to Google and leveling the playing field a bit more. |
how do you figure one is more difficult to scrape than the other?
I wonder how long it will take Google to start allowing you to use it without SOAP?
"Our Web Services are available for non-commercial use unless you first obtain written permission from Yahoo! If you're interested in commercial use of our APIs, Please contact firstname.lastname@example.org for more information."
(From the FAQ)
Is there an easy way to build the Yahoo search services in to a search site?
>> non-commercial use
Their TOS are a little too strict for some parts of the world (as international laws differ), but i don't think using the APIs on a clearly commercial site (ie. one that sells widgets) is in violation of the TOS as long as the use of the API itself is non-commercial - and as long as your site does not deal with any of these subjects:
I understand the TOS to mean that it is the specific use of the API that has to be non commercial. Ie. this is what you say "yes" to when you download:
|d. YOU SHALL NOT: |
(iv) sell, lease, or sublicense the Yahoo! APIs or access thereto or derive income from the use or provision of the Yahoo! APIs, whether for direct commercial or monetary gain or otherwise, without Yahoo!'s prior, express, written permission
So, it's even possible to obtain permission for commercial use (theoretically at least). Anyway, the TOS also has this line:
>> If you have questions about your intended use of the Yahoo! APIs, you may contact us at
Sidenote: It's also the case that you shall not: "use the Yahoo! APIs to operate nuclear facilities" ... *lol*
Damn, it's cool! Great!
Any experience with how up-to-date the Y!-API results are? 'Cause with G API the results are so stale I stopped using them and moved to scraping G serps instead.
just because the G api results aren't identical to what you're seeing in *your* public datacenter doesn't mean it isn't up to date.
I've never seen the api serve something that isn't being shown on at least one datacenter.
> just because the G api results aren't identical to what you're seeing in *your* public datacenter doesn't mean it isn't up to date.
Sorry chap, but this is not what I meant. I saw the API results lagging behind the serps 99% of the time for over a year. That *does* mean that the API was not up to date.
> I've never seen the api serve something that isn't being shown on at least one datacenter.
Me neither. But when I saw a DC serving the same results as the API, that DC's serps were lagging behind the other DC's serps as well. My observations are from 6 months ago, so don't lynch me if the API's topicality has improved since then. I personally swear by scraping.
OK, I worked all night (hey, thanks for that link to yahoo) and got my thing going!
I have integrated it into my 2 phpBB forums!
Check it out at
(shows an orderly table)
(shows a proportional layout
= the thumbnail size is RELATIVE to the picture size
= the bigger the picture, the bigger the thumbnail)
When I first saw this I thought that that looks too confusing. However after a while I didn't want to miss it.
Firefox looks a bit lame, try IE if you can.