/rate_limit_status endpoint sometimes omits data by resource

#1

Hi, I noticed that GET application/rate_limit_status randomly returns empty data for limits by resources.

{u'rate_limit_context': {u'access_token': u'xxxx'}, u'resources': {}}

A new requests to the endpoint with same parameters normally returns the data.

{u'rate_limit_context': {u'access_token': u'xxxx'}, u'resources': {u'application': {u'/application/rate_limit_status': {u'reset': 1527667479, u'limit': 180, u'remaining': 178}}, u'search': {u'/search/tweets': {u'reset': 1527667479, u'limit': 180, u'remaining': 179}}, u'users': {u'/users/suggestions/:slug': {u'reset': 1527667849, u'limit': 15, u'remaining': 15}, u'/users/lookup': {u'reset': 1527667849, u'limit': 900, u'remaining': 900}, u'/users/search': {u'reset': 1527667849, u'limit': 900, u'remaining': 900}, u'/users/suggestions/:slug/members': {u'reset': 1527667849, u'limit': 15, u'remaining': 15}, u'/users/contributors/pending': {u'reset': 1527667849, u'limit': 2000, u'remaining': 2000}, u'/users/show/:id': {u'reset': 1527667849, u'limit': 900, u'remaining': 900}, u'/users/suggestions': {u'reset': 1527667849, u'limit': 15, u'remaining': 15}, u'/users/contributees/pending': {u'reset': 1527667849, u'limit': 200, u'remaining': 200}, u'/users/report_spam': {u'reset': 1527667849, u'limit': 15, u'remaining': 15}, u'/users/profile_banner': {u'reset': 1527667849, u'limit': 180, u'remaining': 180}, u'/users/derived_info': {u'reset': 1527667849, u'limit': 15, u'remaining': 15}}, u'statuses': {u'/statuses/retweets_of_me': {u'reset': 1527667849, u'limit': 75, u'remaining': 75}, u'/statuses/retweeters/ids': {u'reset': 1527667849, u'limit': 75, u'remaining': 75}, u'/statuses/mentions_timeline': {u'reset': 1527667849, u'limit': 75, u'remaining': 75}, u'/statuses/user_timeline': {u'reset': 1527667849, u'limit': 900, u'remaining': 900}, u'/statuses/lookup': {u'reset': 1527667849, u'limit': 900, u'remaining': 900}, u'/statuses/oembed': {u'reset': 1527667849, u'limit': 180, u'remaining': 180}, u'/statuses/show/:id': {u'reset': 1527667849, u'limit': 900, u'remaining': 900}, u'/statuses/friends': {u'reset': 1527667849, u'limit': 15, u'remaining': 15}, u'/statuses/home_timeline': {u'reset': 1527667849, u'limit': 15, u'remaining': 15}, u'/statuses/retweets/:id': {u'reset': 1527667849, u'limit': 75, u'remaining': 75}}}}

I’m using tweepy to access the API. The issue seemed to start on May, 29.

Kind regards

Application Rate Limit Status - broken?
#2

I am also facing the same issue since 2 days now. Any inputs on this is much appreciated.

#3

Also facing this issue. I wonder if it’s not to force using only resources that are needed?

You may also issue requests to this method without any parameters to receive a map of all rate limited GET methods. If your application only uses a few of methods, you should explicitly provide a resources parameter with the specified resource families you work with.

https://developer.twitter.com/en/docs/developer-utilities/rate-limit-status/api-reference/get-application-rate_limit_status

Though, I didn’t notice prior warning about this change.

#4

Same for me.
GET https://api.twitter.com/1.1/application/rate_limit_status.json
returns

{
    "rate_limit_context": {
        "access_token": "token was here"
    },
    "resources": {}
}

Yeah, no warning and it’s just unexpected.
For me - specifying resources like https://api.twitter.com/1.1/application/rate_limit_status.json?resources=users is not working.

#5

tweetinvi is also not working when used with RateLimitTrackerMode

so it is caused by twitter?

#6

same here . my software also not working since 2 days when using RateLimitTrackerMode

#7

I confirm it no longer works now even by specifying a resource… What’s happening there?

#8

Duplicate of Application Rate Limit Status - broken? - closing this one to consolidate.

#9