Issue with max_id parameter

api

#1

Hi There,

I’m using max_id and since_id to iterate through a user’s timeline. I expect the response to return ids less than (or equal) the max_id, but that isn’t happening. Instead it’s returning ids greater (or equal) than the max_id. For example, if I request statuses/user_timeline.json with the following parameters:

max_id: 618096784389349375
count: "10"
include_rts: "0"

I get back the following ids:

636204710656122880
628505715024510976
627472484858773504
619558894042529792
619558146676269056 
618096784389349376 

There’s only 6 because of the include_rts which is fine, but the ids are clearly going the wrong way.

Is anyone else experiencing something similar? Or have I misinterpreted the API?

Any advice would be appreciated!

Thanks!


#2

It works for me. Your output is more consistent with since_id rather than max_id. I would double check your code to see if that is not the case.


#3

Thanks for the response! Yep it’s odd - I’m not using since_id (although I will eventually). That’s what really catching me - it’s exactly the functionality I’d expect from since_id. Thanks anyway, I’ll keep looking :smile:


#4

Hi,

Can you please share the sample signature using both Since_id and Max_id ?
I have tried so many times but it’s not working.

since_id=638474108565594113&max_id=751398817598214144&screen_name=McDonalds&count=3200

Regards,
Aswinikumar