What is the query limit on Yahoo's Finance API? - api

What is the query limit for Yahoo's Finance API? Or where is the documentation that describes the limit?
For all of Yahoo's API's I've only been able to find general documentation for all API's. If you know where the documentation is for Yahoo's Finance API that'd also be appreciated. (I've been searching for a few days on Google, and on Yahoo's API sites, finally turned to friends at SO)
Thanks!

A 2020 update:
YQL was terminated on Jan, 3, 2019Because of this, the older answers in the questions are no longer valid. Archive has a backup of the link they mention from the day before the shutdownYou'll probably never need it, the limits have been changed anyway
Yahoo finance itself was also stopped for a while, but it's available again.It's located at https://query1.finance.yahoo.com/v7/finance (e.g. https://query1.finance.yahoo.com/v7/finance/quote?symbols=AMZN)
I also wondered about the new limits but I can't find an official answer. Online everyone seems to have another answer, but it general it boils down "a 4 digit number" every hour when using the unauthenticated (free) version.

UPDATE:
Rate limits in YQL are based on your authentication. If you use IP-based authentication, then you are limited to 2,000 calls/hour/IP to the public YQL Web service URL (/v1/public/) or 20,000 calls/hour/IP to the private YQL Web service URL (/v1/yql/) that requires OAuth authorization. See the YQL Web Service URLs for the public and private URLs. Applications (identified by an Access Key) are limited to 100,000 calls/day/key*.
However, in order to make sure the service is available for everyone we ask that you don't call YQL more than 0.2 times/second or 1,000 times/hour for IP authenticated users and 2.7 times/second or 10,000 times/hour.

See the Yahoo Query Language Usage Information and Limits page. This is for all of the YQL APIs, not just the Finance API.
YQL Rate Limits:
What this means:
Using the Public API (without authentication), you are limited to
2,000 requests per hour per IP (or up to a total of 48,000 requests a day).
Using the Private API (with OAuth authentication using an API Key), you are limited to
20,000 requests per hour per IP and you are limited to 100,000 requests per day per API Key.
The above answer was originally posted here by me.

Yahoo's YQL allows you to query Yahoo! Finance data. Their usage limits are as follows:
Unauthenticated: up to 1,000 calls/day
Authenticated: up to 100,000 calls/day
See Yahoo's Query language FAQ for more details at http://developer.yahoo.com/yql/faq/

Related

How to get unblocked after exceeding the Google Geocode API usage limit?

Have searched for answers on this for 2 days now with very little luck.
I'm developing a Drupal 7 site which has a Geofield field being autopopulated from an address field using the Google Geocoder API, but as of a couple of days ago this stopped working:
Exception: Google API returned bad status.\nStatus: OVER_QUERY_LIMIT in geocoder_google() (line 52 of /home/.../modules/geocoder/plugins/geocoder_handler/google.inc).
I can remove the proximity search filter that is sending too many requests to the Google API but I can't progress because I run into the above error every time I try to add a new record to the database (which just does one lookup to get a geocode from an address field but fails). Is there any way to unblock my site from Google's API or reset my usage? I've added an API key but to no avail. This was all working fine up until very recently, which I guess is when I unknowingly exceeded the usage limit.
I have limited API experience and am a Drupal/PHP beginner so please be gentle! Happy to provide more info, code, error messages etc if needed. Relevant Drupal 7 modules being used are OpenLayers, OpenLayers Proximity, Geofield, GeoPHP and Geocoder. Thanks for any help anyone can offer.
From Google Geocode Documentation:
Use of the Google Geocoding API is subject to a query limit of 2,500 geolocation requests per day. (User of Google Maps API for Business may perform up to 100,000 requests per day.) This limit is enforced to prevent abuse and/or repurposing of the Geocoding API, and this limit may be changed in the future without notice. Additionally, we enforce a request rate limit to prevent abuse of the service. If you exceed the 24-hour limit or otherwise abuse the service, the Geocoding API may stop working for you temporarily. If you continue to exceed this limit, your access to the Geocoding API may be blocked.
So, I guess you have to wait 24 hours, or upgrade to the business version.

Google Place API usage limitations and billing

I have developed one app in which i have used the Google Place API. This is what places doc says about limitation.
The Google Places API has the following query limits:
Users with an API key are allowed 1 000 requests per 24 hour period.
Users who have also verified their identity through the APIs console are allowed 100 000 requests per 24 hour period. A credit card is required for verification, by enabling billing in the console. Your card will not be charged for use of the Places API.
So my question is that if i enable billing for Place API then its free? Is it really true?
Yes, you will have what they are saying. I have done that, so I can confirm... If you put your credit card info, you are letting them know that you are a verified user, and that therefore you won't misuse their services.
And for the second question, we are talking about Google here. It is really true, you won't be charged, they can make money from other sources :)
EDIT:
Actually, if you need more than the "verified" option, it seems you can contact them as stated by Thor Mitchell (Product Manager #Google) in this topic at Quora: Pros and Cons of Places API
"The limits on use (after identity verification) is 100,000 requests
per day, and we're happy to talk to developers who need more about
their requirements."
As of today, the limit is 150,000 free requests per day, but the documentation is hard to make sense of in terms of how they bill overage.
Latest update March 2019:
"For an overview of pricing for the Google Maps Platform products, please see the Pricing Sheet.
To learn more about how Google Maps Platform APIs are billed, please see Understanding billing for Maps, Routes, and Places."

Google Web Search API (Deprecated) requests limit

Developer's Guid for Google Web Search API (Deprecated) informs, that the number of requests you may make per day will be limited. But I can't find information about how much requests I can make... What the limitation is?
It looks like the limit is 1000 requests per day:
http://code.google.com/apis/soapsearch/api_faq.html#tech7

Alternative to the deprecated google REST web search API

I have been using the Google Websearch API for over 1 year now. The service was deprecated in Nov 2010 but continues to provide results to date. More recently, google has started to enforce the 1,000 queries (?) per day limit on this deprecated service. I swear, last month I made over 10,000 API calls in one day without any errors from the service (same IP, same API key).
So I guess my question is has anyone found an alternative yet? I know yahoo boss is pretty good but I am working exclusively on Google for my projects. I do not mind spending money for for this service either as long as i can get 64 results from Google.
On that thought, how are services like Zoomrank able to bypass all Google limits? I have a subscription with Zoomrank and I can get daily rankings for all my keywords. Do they have a tie-up with Google or are they just accessing some secret service I don't know about.
Some people have suggested the new Google custom search, but i dont know how does that help me search the web? Google CS is limited to the CSE you create and searches within those engines. If I am looking for web results for Pizza, Google CS doesnt help me.
Thanks for your input. Much appreciated
UPDATE: #ggez44 points to some official Google documentation of the solution described below here: http://support.google.com/customsearch/bin/answer.py?hl=en&answer=1210656
You can use the Google Custom Search Engine to search the entire web.
In brief:
Create a CSE that searches a single site (e.g. google.com)
In the CSE control panel's Basics section, set to "Search the entire web but emphasize certain sites"
In the Sites section, delete the single site that you added when you created the CSE
Full details here:
http://www.google.com/support/forum/p/customsearch/thread?tid=56c0bd92dda351b7&hl=en&fid=56c0bd92dda351b7000495e3f500d83f
Once that's implemented, you can enable billing in the Google API Console at a CPM of $5, to a total of 10,000 queries.
Google API Console: https://code.google.com/apis/console/
Pricing: https://code.google.com/apis/customsearch/v1/overview.html#Pricing

Google API Request Limit

Does anyone know where I can find Google API Request Limits for their different services?
On simulating 500+ concurrent users it seems to fail silently fairly often (maybe 1 in 10 loads)
Any ideas?
The information is in their support resources. I am not aware of a central place, but it's all there. Searching the docs for "request limit" should usually do the trick.
The Geocoding API's limits for example can be found here.
Google Maps API Web Services and Google Static Maps API limits were cut effective a few days ago. Starting October 1st 2011 commercial web sites and apps using Google Maps API for free receive:
max of 2,500 calls/day, if modified using Styled Maps feature
max of 25,000 calls/day in total
Fusion tables are preferable to the Google Maps API alone, particularly with respect to rate limits:
Applications using the Google Fusion Tables API can send a maximum of
5 requests per second to the Google Fusion Tables server.
I think they removed the limit recently: can't even find a mention of it in documentation pages where I know for sure that it was mentioned and read about the limit removal somewhere this summer.
Even their new EULA states that their service is not limited but they remain free to limit it however they want at any moment.
500 concurrent users doesn't seem to be that much though, even if limitations where in place; are you sure it's Google what's failing?