Hi there,
Can you try and record the new X-RateLimit-* headers on your
request? We added those because there have been many reports of
incorrect rate limiting that turned out to be incorrect credentials on
rate_limit_status. This is especially common from web browsers; since
rate_limit_status does not require credentials they do not send them.
Let me know if that reflects the problem as well.
Thanks;
— Matt Sanford / @mzsanford
On Apr 2, 2009, at 09:21 AM, @crisatunity wrote:
On Mar 26, 10:45 pm, colboy <[email protected]> wrote:
I'm certainly using credentials. I'm using Tweetdeck and it says
I've
over my API limit. My application can't do any gets, as expected, but
when I do "account/rate_limit_status" it says I have 91 remaining as
shown here, which is the XML I receive when I plug the URL in with
authentication via the website
<hash>
<reset-time type="datetime">2009-03-27T04:32:35+00:00</reset-time>
<reset-time-in-seconds type="integer">1238128355</reset-time-in-
seconds>
<remaining-hitstype="integer">91</remaining-hits>
<hourly-limit type="integer">100</hourly-limit>
</hash>
Any ideas? Am I missing something obvious?
Colin
I am experiencing this identical situation. All my requests are
credentialed and behave as so, except this feature of the API. I get
a non-credentialed response every time.
Michael