The rate limits change through the day, not always fixed to 350. Are they 
staying at 150 all the time? Check over a period of time to see if so.

On 17 May 2011, at 15:38, SN Testing wrote:

> We are using OAuth, but the rate limit headers still show 150.
> 
> request:
> http://api.twitter.com/users/show.xml?user_id=84609847|Authorization:
> OAuth realm="twitterapis.com",
> oauth_signature="cnN6riZwgneJpfhN8C5%2Fh05TAOw%3D",
> oauth_version="1.0", oauth_nonce="f919ce47-d573-2f99-b95b-
> fe33e080f4fd", oauth_signature_method="HMAC-SHA1",
> oauth_consumer_key="djZv4sYbtz8tgE6LMpKaHg", oauth_token="84609847-
> w3YWg9p4QVwkLXJdNOmh8HiTKuvLYfkWhlNl3y1Lf",
> oauth_timestamp="1305641118"
> 
> response headers:
> Accept-Encoding|X-Frame-Options: SAMEORIGIN|X-MID:
> 9d414127f5ae158a149a977884329095e2ebf564|X-RateLimit-Class: api|X-
> RateLimit-Limit: 150|X-RateLimit-Remaining: 149|X-RateLimit-Reset:
> 1305644719|X-Revision: DEV|X-Runtime: 0.04386|X-Transaction:
> 1305641119-79517-32953|X-Transaction-Mask:
> a6183ffa5f8ca943ff1b53b5644ef114be3e990c
> 
> is this a bug?
> 
> -- 
> Twitter developer documentation and resources: https://dev.twitter.com/doc
> API updates via Twitter: https://twitter.com/twitterapi
> Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
> Change your membership to this group: 
> https://groups.google.com/forum/#!forum/twitter-development-talk

--
Scott Wilcox

@dordotky | sc...@dor.ky | http://dor.ky
+44 (0) 7538 842418 | +1 (646) 827-0580



-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Reply via email to