Rate limits have been introduced, as discussed here:
https://developers.soundcloud.com/docs/api/rate-limits
It is not clear what "client application" means in this context. Is the rate limit per client ID or per unique browser/device?
A "client application" refers to an individual application under your developer account on soundcloud.com. Each client application has a set of client credentials, which consist of a client id and client secret pair.
The rate limits are currently being determined per client id, although this may change in the future.
Related
I have a use case where I have to run the github search APIs repeatedly. However sometimes in between I get the error below:
"API rate limit exceeded for user ID XXXXX".
How Can I avoid this error? Is there any way?
Github rest api has following rate limit:
For unauthenticated requests, the rate limit allows for up to 60 requests per hour. Unauthenticated requests are associated with the originating IP address
For authenticated requests(either by OAuth applications or by a personal access token), the rate limit allows for up to 5,000 requests per hour and per authenticated user.
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
Although asked multiple times by users, I still feel uncomfortable with the theory behind.
I am using mongodb as a database for storing certain activities created by users (authenticated via facebook). For efficiency reasons, I want to store their profile picture URL along with the event (de-normalization in a event collection).
When the events are fetched from the database (by random visitors of my website), the profile pictures are rendered client side via:
<img src="https://graph.facebook.com/USERID/picture">
no access-token (due to security on the client side)
preferably lazy loaded...
For my understanding, the rate limit would become a problem, when I would do multiple request to the same profile picture server-side without passing an access token. (same request from same IP address)
Does the rate limit count against IP addresses? If so, only website visitors that
overrun the rate limit would have a problem whereas the same picture would still render just fine for other website visitors (different IP address) - is this correct?
To sum up:
server side requests to the graph API should be made with an access token (this applies the rate to an individual user... necessary because 1 server IP)
client side requests are made from different IP addresses anyway... so no access token required since every client (different IP address) counts against the individual limit
Are these assumptions correct?
If you absolutely wanted to nab those profile pictures you could do so client side as well. You could use a javascript file uploader and upload an off-screen facebook profile picture to your servers. Each user of your application could do some of the uploading for you.
Probably a huge violation of someone's terms of service, but an interesting thought experiment.
I am working on a project that want to use facebook api's. I want to know whether there is a rate limit on the facebook api's per account.
Yes there is a rate limit for Facebook API which is also mentioned in their Platform Policies as
If you exceed, or plan to exceed, any of the following thresholds please contact us as you may be subject to additional terms: (>5M MAU) or (>100M API calls per day) or (>50M impressions per day).
Aside from the Platform Policies mentioned in the pervious answer, the Facebook graph API is subject to multiple level of rate limiting / throttling -- user (access token) level, app level (app id), API level, and IP address.
This doc. has most of what you need: https://developers.facebook.com/docs/reference/ads-api/api-rate-limiting/, other than the IP level throttling.
This post cover the IP level throttling: Facebook Graph API limit - per token and per IP?
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/