I've been trying to get all tweets of a some public(unlocked) twitter user.
I'm using the REST API:
http://api.twitter.com/1/statuses/user_timeline.json?screen_name=andy_murray&count=200&page=1'
While going over the 16 pages (page param) it allows, thus getting 3200 tweets which is ok.
BUT then I discovered the rate limit for such calls is 150 per hour(!!!), meaning like less than 10 user queries in an hour (16 pages each). (350 are allowed if u authenticate, still very low number)
Any ideas on how to solve this? the streaming\search APIs don't seem appropriate(?), and there are some web services out there that do seem to have this data.
Thanks
You can either queue up the requests and make them as the rate limit allows or you can make authenticated requests as multiple users. Each users has 350 requests/hour.
One approach would be to use the streaming API (or perhaps the more specific user streams, if that's better suited to your application) to start collecting all tweets as they occur from your target user(s) without having to bother with the traditional rate limits, and then use the REST API to backfill those users' historical tweets.
Granted, you only have 350 authenticated requests per hour, but if you run your harvester around the clock, that's still 1,680,000 tweets per day (350 requests/hour * 24 hours/day * 200 tweets/request).
So, for example, if you decided to pull 1,000 tweets per user per day (5 API calls # 200 tweets per call), you could run through 1,680 user timelines per day (70 timelines per hour). Then, on the next day, begin where you left off by harvesting the next 1,000 tweets using the oldest status ID per user as the max_id parameter in your statuses/user_timeline request.
The streaming API will keep you abreast of any new statuses your target users tweet, and the REST API calls will pretty quickly, in about four days, start running into Twitter's fetch limit for those users' historical tweets. After that, you can add additional users to fetch going forward from the streaming endpoint by adding them to the follow list, and you can stop fetching historical tweets for those users that have maxed out, and start fetching a new target group's tweets.
The Search API would seem to be appropriate for your needs, since you can search on screen name. The Search API rate limit is higher than the REST API rate limit.
Related
Need a clarification on this:
As per docs "By default, a search result set identifies matching video, channel, and playlist resources", how this matching takes place, do they search on comments also, any idea on this.
Thanks !!
The YouTube api operates on the same rate limits as the other google apis.
There are project based limits and user based limits.
You can see the limits on google developer console.
My project can make a max 1800000 requests per minute
It also has a quota cost limit of 10000 which is not really what it sound like.
Then each user can make a max of 180000 request per minute.
This not related to the amount of data a user has on their account. Its strictly related to the number of requests or the cost of the request your application or a user can make over a period of time.
You can request additional daily quota over the development 10k if you want. Just submit the form over on google cloud console.
I am not aware of increased abilities with YouTube APIs for big YouTube channels.
I did a Twitter clone using rails api + react, just for study purposes.
I have quite simple logic of requests: click in a user, load its informations and tweets, requesting for the api. However, If I do this fast like 3 times, I receive the status 429 (too many requests) with the header Retry-After: 5.
There is a way to increase the number of requests in a given time? How would be the correct approach to handle with this in such common situation?
From my understanding, the error information you have shown is correct, It means request cannot be served due to the application's rate limit having been peaked for the resource.
Rate limits are divided into 15 minute intervals. All endpoints
require authentication, so there is no concept of unauthenticated
calls and rate limits.
To overcome this situation, here is an example from the documentation itself.
I´m trying to retrieve a big amount of tweets, like 1000 or 3000 per minute, now I´m using the public API of twitter with the URL:
https://api.twitter.com/1.1/search/tweets.json?q=#whatever+OR+#whatever&since=15-05-2015&count=100&result_type=recent
but the problem is that I need more than 100 tweets because Twitter only supports 180 request every 15 mins, and always I need more than than, my question is that if there is somewhere a twitter API that can do what the public API but can retrieve more than 100 tweets per request.
The sort answer is that there is no legitimate way to get around the rate limits of the Rest API.
You can request "whitelisting" for your application, but Twitter doesn't do it very often and not for average users.
The Streaming API might provide the specific functionality that you're looking for.
I'm working on a kind of a twitter wall. Users can login with twitter and create their own wall, which will display the tweets for certain terms/hashtags.
I'm still looking for the best strategy to get the data out of the Twitter APIs.
Following some of my thoughts:
Strategy 1: Streaming API
Open a single stream (POST statuses/filter) for all walls
Each hashtag is added to the track parameter
When new tweets arrive, they will be processed and sent to the corresponding wall
("one account, one application, one open connection" cf. https://dev.twitter.com/discussions/14935)
Problems with the Streaming API
Streaming api is limited to 400 keywords to track
What to do if there are more than 400 keywords to track?
Streaming api is limited to 1% of the tweets of the firehose
It's very difficult to get above 1% of the firehose, but if you're tracking a term like "apple" it'd be pretty easy to exceed the 1%. (cf. https://dev.twitter.com/discussions/6349)
How can I handle such popular terms? Blacklist them?
Strategy 2: REST Search API
Store user access tokens
Poll the Search API (GET search/tweets) on behalf of the user, respecting the rate limits of 180 queries per 15 minute
(cf. https://dev.twitter.com/discussions/11141)
Problems with the REST Search API
Polling
Could get very expensive to poll the API for a lot of users.
Do you have any suggestions/recommendations which strategy would fit the best? Are there already solutions for these problems?
Best regards
I've been reading Twitter's documentation on this but I'm a bit confused because I'm new to both the API and oauth. If I get a user to login to Twitter using oAuth does that mean that the rate limit would be 350 requests for their account and not my application? In other words, is the rate limiting applied to each account used individually or 350 for my application?
From the FAQ:
Are rate limits per user, per computer or per application?
Rate limits apply in different ways. Some methods are rate limited
whilst others are fair use limited. In the majority of methods GET
(read) requests are rate limited and POST (write) methods are not. You
should check the rate limited section of the documentation for the
method you want to use to make sure.
We apply requests to rate limits in the following ways:
Rate limits for authenticated requests are applied to the user.
Rate limits for unauthenticated requests are applied to the IP that
we see.
This means applications share the unauthenticated rate limit AND the
authenticated limit. The application being used makes no difference so
switching between multiple clients on the same IP offers no rate limit
advantage – they will all share the same remaining requests.
Multiple user accounts in a Twitter client each have their own user
rate limit but share the unauthenticated requests.
Search has it's own rate limit and as all requests are anonymous it
applies to the IP we see. This means all users on the same IP share
the search rate limit.
This means that every request which you'll be doing for an authenticated user (OAuth) will check this user's rate limit, while any general non authenticated request you'll make will check your application's IP rate limit.
Javascript, Client side request - users rate limit.
Serverside request - web applications rate limit.
Client application using streaming API - no rate limit (technically
not true, but a rate limit that you won't need to worry about because
your limited in another way based on the information you track
instead and the stream updates you at a limit below the cap)
for more, look at the duplicate question, the FAQ link that was posted, and the rate limiting doc,
https://dev.twitter.com/docs/rate-limiting