This project has moved and is read-only. For the latest updates, please go here.

Getting 1,500 statuses

Dec 20, 2010 at 7:34 AM
Edited Dec 20, 2010 at 7:34 AM

Hi guys!

I love the tool! The new version kicks ass compared to a year ago when I got it... Great work :)

Anyway, I have a need to get the max amount of "tweets" on a query to Twitter. According to Twitter here on the bottom: "Clients may request up to 1,500 statuses via the page and rpp parameters for the search method."

Even looking here, I see the limits:

And in Linq to Twitter you have the Page and PageSize options when searching.

I'm not 100% sure, though to get all 1500 results, would I have to call Twitter 15 times (page 1-15)?



Dec 20, 2010 at 1:26 PM

Hi Daniel,

Thanks. Yes, you'll have to call Twitter for each page.  The method of paging and what is returned can be different for each Twitter API query type.  Some queries use cursors, which is the preferred method if cursors are available.  You can see examples in my API docs and sample code on how to do paging with the particular API you're using.  Come back an ask for clarification if you don't find what you need.


Dec 20, 2010 at 6:25 PM

Hey Joe,

Thanks for the response. I'm using the generic search, so that doesn't have a cursor... I'll have to test it a bit and play with the page and pagesize.



Dec 22, 2010 at 2:03 AM

Search might be a little strange because Twitter has an arbitrary cut-off point for how far back you can go.  So, even if they document up to 1500, you might get much less, depending on the date up to which they stop returning results.  My best guess is that the behavior is linked to scalability.