> > I'd like to pull about 1950 statuses, all of my updates, in one API > connection. > Is my limit 200 per API request (requiring 10 API requests) OR is my limit > 1950 in one API request?
You can get 200 statuses per requests. Therefore you will have to use 10 calls to retrieve 1950 statuses. Paging in this way is the most effective, server friendly way to do this. Doug Williams Twitter API Support http://twitter.com/dougw On Sat, Apr 18, 2009 at 1:07 PM, Khyron <[email protected]> wrote: > I see the 2 following statements made, in the following order within > moments > of each other at http://apiwiki.twitter.com/REST+API+Documentation. > > > Under "Pagination Limiting": > > "Clients may request up to 3,200 statuses via the page and count > parameters. Requests for more than the limit will result in a reply with a > status code of 200 and an empty result in the format requested." > > Under "Be Nice to the Servers": > > "If your application keeps a local archive that persists between sessions, > it's > okay to request an entire timeline up to 200 statuses." > > > So I can only request up to 200 statuses even though the limit using page > or count is 3200? What gives? > > I'd like to pull about 1950 statuses, all of my updates, in one API > connection. > Is my limit 200 per API request (requiring 10 API requests) OR is my limit > 1950 in one API request? Are there other parameters besides page and > count which are more server friendly, thus allowing larger requests? > > What am I missing? Can someone clarify please? Now that I figured out > how to do what I want to do, I want to make sure that I play by the rules > so that I don't get blacklisted for killing the servers. > > Thanks in advance yet again! > > -- > "You can choose your friends, you can choose the deals." - Equity Private > > AlphaGuy - http://alphaguy.blogspot.com > On Twitter - @khyron4eva > >
