Hi Doug, I tried the approach that Karthik mentioned but it didn't quite work.
So after the first 15 pages worth of tweets were retrieved, I set the max_id to the id of the last tweet and page =1 For example, id of last tweet = 1000 max_id = 1000 page = 1 then the next query (for the next 15 pages) http://search...?max_id=1000&since_id=100&page=1... The results returned basically ignored the max_id and the ids were all greater than the stipulated 1000. Any idea why the max_id was ignored ? Is there a way to retrieve tweets beyond 15 pages? Thanks for the help in advance, Ronnie On Mar 10, 4:45 pm, Doug Williams <[email protected]> wrote: > Nish, > The way I read your question, it sounds like you are trying to use the > max_id parameter incorrectly. max_id allows you to specify the maximum > status id to return. It is the way to limit the results to statuses before a > given status id. It is complementary to the since_id parameter, capping the > results of a query at the top of the result list where since_id closes the > bottom. > > Doug Williams > Twitter API Supporthttp://twitter.com/dougw > > On Tue, Mar 10, 2009 at 7:20 PM, nish <[email protected]> wrote: > > > Hi, > > > Were you able to get more than 1500 tweets using the max_id method? > > > I somehow cannot get it. I am using the search JSON API and whenever > > I set the max_id looks like the server resets it to something else. > > > Thanks. > > > On Feb 24, 11:59 am, Karthik <[email protected]> wrote: > > > Please confirm, if the following is allowed? > > > > 1. Set rpp=100 and retrieve 15 pages search results by incrementing > > > the param 'page' > > > 2. Get the id of the last status on page 15 and set that as the max_id > > > for the next query > > > 3. If we have more results, go to step 1
