YQL Term extraction service rate limits

Hi, I'm building an app that makes use of the YQL term extraction service, but I am having problems when running the service. I very often (90 % of the time) get no results back from the term extraction service, regardless if I use the public or oauth-based authentication.

What are the limits (total, per hour, frequency)?

Thanks, Per

3 Replies
  • You should also try http://developer.yahoo.com/search/content/V2/contentAnalysis.html which latest API offering, Term Extraction service is deprecated now.

    To Further investigate and solve your problem, can you please let me know more detail how you are using this API??

  • Note that if you are using the API as REST URL


    select * from search.termextract where context="Italian sculptors and painters of the renaissance favored the Virgin Mary for inspiration" and query="madonna" http://query.yahooapis.com/v1/public/yql?q=select%20*%20from%20search.termextract%20where%20context%3D%22Italian%20sculptors%20and%20painters%20of%20the%20renaissance%20favored%20the%20Virgin%20Mary%20for%20inspiration%22%20and%20query%3D%22madonna%22&diagnostics=true

    REST url tends to break with large text easily, if url goes even bigger than 1024 characters , it will be blocked client or server somewhere in the chain. For large URL you should use POST.

  • Currently when I use this API it gives me an undocumented block.

    I am still unsure if this is somehow a bug with my script or if this is a desired thing from Yahoo.

    After about 500 requests to the end point, regardless of IP it seems to block me by giving empty results no matter the content used.

    Just for the fun of it, i put together some mock query which was run hundreds of times that I know returns results and somewhere between 400 and 500 it seems to stop returning results. It gives no failure, or no blocked notice.


Recent Posts

in General Discussion at YDN