Hi Jon,
The search and main twitter.com APIs use different rate limiting
[1] so search.json is not expected to have those headers.
Thanks;
— Matt Sanford / @mzsanford
[1] - http://apiwiki.twitter.com/Rate-limiting
On Apr 20, 2009, at 09:14 AM, obeymiffy wrote:
On a related note, i'm finding that these params
* X-RateLimit-Limit
* X-RateLimit-Remaining
* X-RateLimit-Reset
only seem to get returned to me when i call the account/
rate_limit_status endpoint. And even though the docs say that it
should not count against the API limit, they are the only call that
shows that count being decremented.
I've double checked that my calls are GET and i'm using the
search.json endpoint with very simple queries. Am I missing
something? I'd like to track that number so that I know if our usage
is going to be near the rate limit.
Regards
Jon
On Apr 17, 11:14 am, Doug Williams <[email protected]> wrote:
It is the number of hits you have left until the reset-time is hit.
So it's
part of that rolling window.
<?xml version="1.0" encoding="UTF-8"?>
<hash>
<remaining-hits type="integer">19933</remaining-hits>
<hourly-limit type="integer">20000</hourly-limit>
<reset-time type="datetime">2009-04-08T21:57:23+00:00</reset-time>
<reset-time-in-seconds type="integer">1239227843</reset-time-in-
seconds>
</hash>
Doug Williams
Twitter API Supporthttp://twitter.com/dougw
On Fri, Apr 17, 2009 at 6:27 AM, Dimebrain
<[email protected]> wrote:
I just realized I don't know whether the remaining_hits element
returned for /account/rate_limit_status is a static number from the
beginning of the current hour, or if it is the remaining hits on a
rolling sixty minute cycle. Does anyone know?
