Application Rate Limit Status - broken?

[mostman1043]

Anyone running into an issue using the application/rate_limit_status endpoint? Starting today it is returning an empty object for resources

[vladhosu]

@mostman1043 Same here, it doesn’t seem to work properly.

There’s another thread here: /rate_limit_status endpoint sometimes omits data by resource

[lancasterboxreg]

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": {}
}

[ThirstToJustice]

yep broken my software since 2 days

using tweetinvi

[andypiper]

Thanks for raising this. Investigating internally. In the meantime, I suggest using the x-rate-limit HTTP headers to track your limits (note that these are only valid with GET requests, and only for standard API endpoints).

[lancasterboxreg]

@andypiper, thanks for update!
What to do about POST requests? Cause app can be blocked if limits are reached, right? We can’t just get rid of that check for now while you are investigating.
And what endpoints are standard?

[ThirstToJustice]

so when can we expect fix of the api? our application is not working since 2 days almost

[andypiper]

The rate_limit_status endpoint has never carried data about POST endpoints. Per the documentation, POST limits are account limits. You should continue to treat those in the same way. I’d also encourage you to use the HTTP headers in place of the rate_limit_status endpoint where possible, since it reduces the number of API calls you need to make in order to keep track of your call quota.

[andypiper]

We are unable to provide an ETA at this time. There should be no reason that this specific endpoint blocks you from using the API generally, so long as you pay attention to the documented rate limits in your application (or use the HTTP headers to track usage).

[sqlcnet]

Thanks Andy. I trust that this issue is getting top priority status. Correct? There may be workarounds but it seems ridiculous for us to re-code our applications in a panic given this is something broken on Twitter’s end.

[andypiper]

We’ve identified the deployment that temporarily caused this issue over the past ~24 hours, and apologise for the problems it caused to many of you. We’ve rolled back the change, and will monitor for further issues in this area.

We appreciate your patience while we’ve been investigating!

[andypiper]