Search/tweet X-Rate-Limit-Limit saying 15 when the documentation says 180


#1

On requesting search/tweet i am expecting to get 180 requests per window as per documentation found here: https://dev.twitter.com/docs/api/1.1/get/search/tweets

The returned headers that i am getting are only showing 15 per rate limit window as per these lines

X-Rate-Limit-Limit: 15
X-Rate-Limit-Remaining: 11
X-Rate-Limit-Reset: 1359994330

Here are the full headers

HTTP/1.1 200 OK
X-Access-Level: read-write-directmessages
Content-Type: application/json;charset=utf-8
Last-Modified: Mon, 04 Feb 2013 16:02:04 GMT
Expires: Tue, 31 Mar 1981 05:00:00 GMT
Pragma: no-cache
Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0
Set-Cookie: guest_id=v1%3A135999372460835438; Expires=Wed, 4-Feb-2015 16:02:04 GMT; Path=/; Domain=.twitter.com
Set-Cookie: lang=en
X-Transaction: 3817098805926d8a
X-Frame-Options: SAMEORIGIN
Status: 200 OK
Date: Mon, 04 Feb 2013 16:02:04 GMT
Content-Length: 5514
X-Rate-Limit-Limit: 15
X-Rate-Limit-Remaining: 11
X-Rate-Limit-Reset: 1359994330
Set-Cookie: k=92.232.166.241.3817098805926d8a; path=/; expires=Mon, 11-Feb-2013 16:02:04 UTC; domain=.com; httponly
Server: tfe

What’s this all about then?


#2

Can you share an example of the URL you’re executing in this case?


#3
https://api.twitter.com/1.1//search/tweets.json ?count=100 &oauth_consumer_key=XXX &oauth_nonce=XXX &oauth_signature=XXX &oauth_signature_method=HMAC-SHA1 &oauth_timestamp=1359996793 &oauth_token=XXX &oauth_version=1.0 &q=angularjs &since_id=298474170222772224

#4

Are you actually sending those double “//” path items? That’s probably your issue.


#5

Fixed and fixed… thank you. I did not realise that was going to be such a simple one.

Thanks, again