Hi there

We also thought we were not receiving the correct rate limit - however
the account/rate_limit_status method doesn't actually correctly
reflect these new request limits. Instead, you'll need to (at least,
until - or if - Twitter change this method to respond appropriately to
OAuth calls) use the X-RateLimit-Limit HTTP header to detect the
current rate limit. The good news is that the HTTP header *does*
reflect the new 350 RPH limit :-)

I've also just posted about this here:

http://groups.google.com/group/twitter-development-talk/t/b9e2aa61f2af0911

So it might be worth keeping an eye out for @raffi's reply.

Cheers

-N

On Mar 2, 6:47 pm, 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?

Reply via email to