I'm building an app with timely, Facebook statistics (just the total count) associated with web content. The content volume is substantial, and statistics should be updated every few minutes for each url. So the Graph API request count, to http://graph.facebook.com/?id= is massive. Are there limits to the number of requests? I don't batch them.
Only batch limits for apps seem to be communicated:
https://developers.facebook.com/docs/graph-api/making-multiple-requests
You should definitely add an App Access Token, and you should definitely use
/?ids={url1},{url2},{url3},...
to reduce your requests. There are no published actual request limits of the Graph API.
Related
Facebook's API doc says you can only make 200 share count requests per app-user every hour (https://developers.facebook.com/docs/graph-api/advanced/rate-limiting) but I just made 200K share count requests in less than 60 minutes and I didn't get any rate limiting header. I want to see the X-App-Usage HTTP header to code something in order to handle it. Do you know if Facebook is really rate limiting share count requests?
In addition, the Application Rate Limiting Chart is always showing nothing:
Thanks for reading!
On Facebook's documentation for Rate Limiting on the Graph API (shortcut to App-Level limits), I found this little note:
Caveats:
Not all API calls are subject to rate limits, so the number of calls you make may not match what you see in the rate limit tool.
Does anyone know if there is a way to increase the quota limit of 10 queries when batching calls to the core reporting API?
This question/answer mentions the limit of 10: How can I combine/speed up multiple API calls to improve performance?
If I try to add more than 10 queries to the batch only the first ten are processed, each one after that contains a 403 quota exceeded error.
Is there a pay option? Would love to speed up the process of reporting on GA data for a bunch of URLs. I looked in my Google Developer's Console under the Analytics API where there is an option to increase the per-user limit and a link to request additional quota but I don't need total quota to increase, only allowed batch requests.
Thanks!
Quota is the number of requests you are allowed to make to a Google API without requesting permission to access more. Most of the Google APIs have a free quota, a number of requests Google lets you make without asking for permission to make more request. There are project based quotas and user based quotas.
Unless it says other wise APIs Quotas are projects based not user based.
User quota example
Per-user limit 10 requests/second/user
Some Quotas are user based, a user is normally the person that has authenticated the request. Every request sent to google contains information about who is making the request in the form of the IP address where the request came from. If you have your code running on a server the IP address is the same all the time so Google sees it as the same user. You can get around his by adding a random Quotauser to your request this will identify the request based upon different users.
If you send to many requests to fast from the same user you will see the following error.
userRateLimitExceeded The request failed because a per-user rate limit
has been reached.
The best way to get around this is to use QuotaUser in all of your requests, and identify different users to Google. Or just send a random number every time should also work.
Answer: You can't apply for an extension of the flood protection user rate limit. But you can get around it by using QuotaUser.
more info on quotas can be found on Google developers console APIs
Dose Facebook limits total api calls (600 call per 600 seconds) for each app separately within one business or the limit apply for all the apps within a business?
for example:
i have a business with 6 apps, each app can make 600 calls per 600 seconds?
or
each app can make 100 calls?
Limits are per App/Token/IP afaik, so it´s always good to use a User or Page Access Token instead of an App Access Token or even no Token at all. But the limit is dynamic, there are no static numbers. And you are not allowed to use several App just to circumvent the API Limit.
More information: What's the Facebook's Graph API call limit?
I am getting an FBerror "This operation can't be completed: Application request limit reached".
Does anybody know why is it so? How to check the limit? How to increase the limit? What depends on the limit allocation?
I recently ran across this issue doing a large number of requests using an application access token (the initial project requirements mandated that the user shouldn't have to authorize the app).
After much frustration, we finally were put in touch with a contact at Facebook who provided the following info in response to my question regarding request limits:
There is a limit, but it's pretty high, it should be difficult to hit unless they're using the same access tokens for all calls and not caching results, etc. It's 600 calls per 600 seconds per access token.
Ultimately we ended up requiring the user to authorize, as Facebook does not seem to distinguish between user access tokens (one token per user) and application access tokens (one token for all users) when calculating its seemingly arbitrary request limits.
If you are running into this error with a user access token, you may need to optimize your API calls (possibly by combining FQL queries or replacing multiple Graph requests with a single FQL query).
try this with your php code:
50 continuous FQL calls. After a pause of 10 seconds (sleep (10)) You repeat.
if($nr%50==0)
{
sleep(10);
echo "\n\n---Bloque #".++$numBloque."---\n\n";
}
IS there a limit of connections and time of requests I can send to the Facebook public API?
I do not need to get private informations of the logged in users, but only some public information.
I will get a LOT of data, and I will have to do a LOT of request.
Is there a limit I have to consider?
There is officially no limit that is specified by the Facebook Dev team. However, users did face issues in the past while trying to pull large amounts of data. I believe there was also a bug that was being tracked some time back regarding this.
Facebook limits API access on multiple levels as e.g. per User ID and per App ID. The calculate a 'score‘ per app that defines individual API limits. This depends e.g. on the number of active users but also on the 'smartness' of the requests as well as their CPU and memory usage on the Facebook side. See this for more details https://developers.facebook.com/docs/reference/ads-api/api-rate-limiting/