Twitter api rate limit is incorrect for statuses/lookup


According to this: the rate limit for an application-only call to statuses/lookup is 180, but when I call application/rate_limit_status, it tells me that my limit is only 60:


I am using restsharp to make these calls, and am using the following code:

//get the application bearer token:
var bearerCredentials = string.Format("{0}:{1}", encodedKey, encodedSecret);
var encodedBearerCredentials = EncodeTo64(bearerCredentials);

var client = new RestClient(TWITTER_API_ENDPOINT);
var request = new RestRequest("oauth2/token", Method.POST);
request.AddHeader("Authorization", string.Format("Basic {0}", encodedBearerCredentials));
request.AddHeader("Content-Type", "application/x-www-form-urlencoded;charset=UTF-8");
request.AddHeader("Host", "");
request.AddHeader("User-Agent", "FanManager");

request.AddParameter("grant_type", "client_credentials");
var response = client.Post<Dictionary<string, string>>(request);
//bearer token comes back successfully

//get rate limit status
var request = new RestRequest("1.1/application/rate_limit_status.json");
request.AddHeader("Authorization", string.Format("Bearer {0}", bearerToken));
var client = new RestClient(TWITTER_API_ENDPOINT);
var response = client.Get<RateLimitResponseDto>(request);

Is there something I’m doing incorrectly on my end? I’m seeing a rate limit of 180 when I use the developer console, which leads me to believe there’s something wrong on my end, but I’ve tried a couple of twitter api libraries (linq2twitter, tweetinvi) and they both return rate limits of 60.


It’s not on your end. It seems the rate limit for app-auth and user-auth are reversed for that endpoint. I’m pretty sure it’s an error on our side, I’ll investigate.