Rate Limit Status Endpoint Doesn't Return how many times I can tweet

restapi

#1

https://dev.twitter.com/rest/reference/get/application/rate_limit_status

That is the page that’s linked to in the “what do I do if I hit Rate Limit Exceeded” when tweeting with the API.

The bad part is that I can’t for the life of me see where (if it exists at all) how many tweets I have left whenever I hit that endpoint. The example payload doesn’t include the data either.

Is this endpoint going to ever include this data? If not can this be stated somewhere?

I know verified users have different limits than non verified but we’d like to be able to more accurately predict how many tweets an hour an account is allowed so we never hit the limit to begin with.

Thanks!


#2

See https://dev.twitter.com/rest/public/rate-limits

POST operations are limits at the account level and not directly managed by the API. There is no intent to add this information to the rate limit status endpoint or the X-Rate-Limit headers (which you’ll find more useful for the read operations than the single endpoint).

There’s no documentation on any potential differences for verified accounts.


#3

Good to know.

It’s too bad the twitter ruby gem seems to be semi abandoned.
There have been PR requests for years to add this data. Since this is now confirmed to be the only way to get at it, maybe I should refresh those PRs.


#4

Thanks for your interest in the gem - I’m looking at tidying up some existing PRs and issues on twurl at the moment, but I’m not sure how much time @sferik and others have had on the gem lately. Hopefully we can work together to make improvements there as well.


#5

Sounds good.

I’m very invested in the gem but the very slow acceptance rate of the PRs makes me not wanna invest time changing it.
I may just fork it instead.

Thanks for all your help so far! :slight_smile: