Hey there,
You can can monitor your current rate limit status by using the
'/1/account/rate_limit_status' endpoint or by checking your X-RateLimit
response headers values. By the way, it looks like the "Current API hits
remaining" data you're reporting is your X-RateLimit-Reset header value. Could
With 1.3 billions API requests remaining I'm going to go out on a limb and
guess that there is an issue on Twitter's side. Hopefully it is a
transient corruption that will just fix itself shortly. If you are using
authentication other users on the same IP should not effect your limit.
Abraham
I have been away from my app for hours and just tried running it
again, with the same 400 error message and bad data:
Current API hits remaining: 1305853176.
Current API Hourly limit: .
Current API Reset Time: Fri May 20 00:59:36 + 2011.
API Method HTTP Code Response Length Parame
