The Twitter's API documentation is quite confusing for me.
It says that rate limits for statuses/update are 300* per user; 300* per app
Does it mean that each of the users can do 300 tweets/retweets? Or it means that all users can do 300 tweets/retweets together per time window?
Thank you for attention!
This announcement may help to clarify the information. At an overall application level, it is not possible to post more than 300 Tweets and/or Retweets inside that window, regardless of the number of users, unless you've applied for elevated access to the API.
Related
I can't find any information on rate limiting with the Google Books API. I'm interested in doing ~300K total ISBN queries to retrieve lists of book categories, and I want to throttle my requests to stay under their limit. I have a developer API key, but not OAuth. Does anyone know what the rate limits are for the Google Books API, or at least have a ballpark?
According to this post,
https://groups.google.com/forum/#!topic/google-api-java-client/_TFuPpAKSew
Around 100k/day is not a problem.
You can also request more quota, if you need it, as follows:
Go to the API Console (https://code.google.com/apis/console)
Select "Quotas" on the left navigation pane.
Click on the "Request more..." link and submit the form.
"Your quota request should be processed within a few business days at most. Basically we want to hear from our developers so we know what type of traffic they are sending, so we can add resources to accommodate them as necessary. But from what you describe, perhaps 100K/day, should not be a problem."
The Dailymotion API documentation indicates that some fields are rate limited (for example stream_h264_hd1080_url for video resource, see on http://www.dailymotion.com/doc/api/obj-video.html).
I could not find any information on this limits in their documentation or via google.
It just seems that the field return null most of the time, and works for a few minutes from time to time. I don't know if this limitation is per user-token or per-application.
Does anybody has information about it ?
All stream_*_url fields are rate-limited to 50 calls per day.
Upload is also limited to 4 per hour.
This field may return null when this quality level is not available or when the user providing the access token is not the owner of the video.
I am working on a project which requires getting tweet and user information from twitter. I can't even test the current system because I keep hitting twitter rate limit. Is there any way around it?
Basic information that I am looking to extract from each status is:
Status text
User follower count
User following count
Retweet count
Geo location co-ordinates
I am using Twitter4J API to do this.
Any help will be appreciated. Thanks in advance.
EDIT
I am using twitter's search API to get list of tweets.
One option is to use a Twitter Data Reseller (e.g. GNIP) who can sell tweets.
Another option is to maximize your use of the API. Here are some tips:
Check Rate Limit Status for each API you're use to make sure you don't go over and when the rate limit resets (currently every 15 minutes).
Look at the parameters to make sure you request a count of the maximum number of tweets for that API. e.g. a count can default to 20, but you can set it to 200, depending availability and limits on the specific endpoint. This potentially reduces the number of queries you have to make.
Page your results according to the Twitter's Working with Timelines guidance. Use SinceID and MaxID to make sure you're only requesting new tweets. This could reduce requests by reducing the number of tweets you need (through increasing the opportunity to stay within max count) and reducing the number of requests by avoiding queries for tweets you already have.
Essentially, you want to examine endpoint parameters with a perspective for how to decrease bandwidth and reduce the number of queries you have to make.
There is a large number of sites like Twitaholic or Twittergrader that offer rankings of Twitter users depending on the number of followers, influence, etc. I haven't found much information, though, on how do they compute these rankings.
My guess is that they begin with a handful users and keep exploring the followers' graph, while periodically updating the information of the users they already know of.
So the question is: is this the right approach or is there a more trivial way of doing it?
The sites you mention started years ago, and at that time they were given whitelisting by Twitter, which means that they can make tens of thousands of API requests per hour. Twitter no longer gives out new whitelisted accounts, so this type of analysis cannot be done by new sites. New accounts are only allowed to make 350 API requests per hour.
It is in fact possible just to use the Twitter API to examine and remember everything about every user, which is what quite a few sites do. twitter streaming api
I am writing a small app, building stats for twitter users (no of tweets, friends etc). I am using this api
http://api.twitter.com/1/users/show.json?user_id=12345
I can only make 150 calls per hour, which is very very small, given the size of twitter. How do companies that rely on Twitter's API manage to overcome this rate limit?
The 150 API calls is per user per application. Larger companies likely broker deals with Twitter.
You need to get whitelisted to get a far higher rate limit. They are open to all sorts of developers, as long as you give a good reason for what you are developing:
http://twitter.com/help/request_whitelisting
You will easily get whitelisted, just apply. They will accept more or less any reasonable application, but just don't want to leave it 'wide open'. If they dont accept you, and you still want to get your hands on the data, just scrape it.