#1

I’m using API 1.1, and I’m checking my rate limits every so often, but I’ve found that when I use the ‘/statuses/user_timeline/:id’, no matter how many calls I make to that endpoint, the “remaining” value in the rate limits response still stays at 180.

Don’t get me wrong, I’m not complaining if it really means I have unlimited calls to that endpoint, but if it means I’ll be tagged for hitting the rate limits when I don’t even know I’m close, that would be quite unpleasant.

#2

I’ve experienced the same behavior.

#3

We’re working to resolve reporting unbalances on this explicit rate limit method – the HTTP headers you get in the response should continue to be accurate in the meantime.

#4

Funny thing, but I’ve managed to fix this by removing the odd “slash” character from request URL (it was put by mistake):

http://api.twitter.com/1.1//statuses/user_timeline.json?screen_name=…

After I changed to

http://api.twitter.com/1.1/statuses/user_timeline.json?screen_name=

application/rate_limit_status started to return the correct value of “remaining”