I reported this bug yesterday. Instead of making that extra call, why
not look at the response headers which come back with each API ACCESS
- you'll get the info you need:
"X-Ratelimit-Limit" = 150;
"X-Ratelimit-Remaining" = 133;
"X-Ratelimit-Reset" = 1267576025;
Andrew Stone
Twitter / @twittelator
http://www.stone.com
got iPhone?
http://j.mp/twitpro
http://j.mp/tweettv-app
On Mar 2, 11:47 am, eclipsed4utoo <ryanalford...@gmail.com> wrote:
> I thought that the OAuth Rate Limit went up to 350? I am still
> getting 150.
>
> Here is the returned XML from my request
> tohttp://api.twitter.com/1/account/rate_limit_status.xml
>
> <?xml version="1.0" encoding="UTF-8"?>
> <hash>
> <reset-time type="datetime">2010-03-02T19:42:28+00:00</reset-time>
> <hourly-limit type="integer">150</hourly-limit>
> <reset-time-in-seconds type="integer">1267558948</reset-time-in-
> seconds>
> <remaining-hits type="integer">150</remaining-hits>
> </hash>
>
> I am using OAuth and using the new "version" of the REST API. What
> else do I need to do?
