This could definitely be made more obvious. To instruct the API to go into "cursoring" mode, append cursor=-1 to your query parameters on the initial request.
GET http://api.twitter.com/1/followers/ids.xml?user_id=158414847&cursor=-1 The response will then contain the cursor fields you're looking for. Taylor On Thu, Dec 9, 2010 at 12:31 AM, Robbie Coleman <[email protected]> wrote: > There is a previous > post<https://groups.google.com/d/msg/twitter-development-talk/iBr1TWdEfCw/hRSyqNoWypUJ> > about > this from 9/2010 without any response and I feared reply there would go > unnoticed, so here is a new post (sorry) > > I cannot get a response json or xml that contains the > documented<http://dev.twitter.com/doc/get/followers/ids> > next_cursor and previous_cursor. And without these, there is no way to > get the full list for users with more followers than the API will return in > a single response. Here are two example twurl links to illustrate this > issue: > > 1. json for user_id 158414847 > (@TheDailyShow<http://twitter.com/#!/Thedailyshow>): > > long_twurl_link<http://dev.twitter.com/console/recall?client_application_id=41837&content_type=json&method=GET¶m-keys%5B%5D=user_id¶m-keys%5B%5D=cursor¶m-vals%5B%5D=158414847¶m-vals%5B%5D=-1&path=followers%2Fids&version=1> > 2. xml for user_id 158414847 > (@TheDailyShow<http://twitter.com/#!/Thedailyshow> > ): > another_long_twurl_link<http://dev.twitter.com/console/recall?client_application_id=41837&content_type=json&method=GET¶m-keys%5B%5D=user_id¶m-keys%5B%5D=cursor¶m-vals%5B%5D=158414847¶m-vals%5B%5D=-1&path=followers%2Fids&version=1> > > Here are the results (abridged): > > json: > > > [ 14784309, 223112592, 184849648, 147520179, 210794450, 221171315, > 169841576, 208912350, 106867628, > > ... > > 7384292, > > 7203292, > > 6633982, > > 6609302, > > 6369362, > > 616113 > ] > > > xml: > > <?xml version="1.0" > encoding="UTF-8"?><ids><id>14784309</id><id>223112592</id><id>184849648</id><id>147520179</id> > > <id>210794450</id> > > <!-- ... --> > > <id>7203292</id><id>6633982</id><id>6609302</id><id>6369362</id><id>616113</id> > > </ids> > > > As you can see, neither have the cursor fields. This is now a showstopper > for my current project and I need a solution fast. Any workarounds out there > would be very helpful as I cannot find a way around this at all, but I > cannot imagine that all apps out there are just as busted as mine right now. > > Thanks, > -- robbie > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
