Monthly Tweet Cap Usage is always 0

[seeminglee]

The tweet cap usage on my developer panel is always 0, even though I’ve used many endpoints to search as well as to tweet.

How can I tell what the usages are? I want to avoid being rate limited but there isn’t a way for me to tell my current usages if the panels always displays 0.

Is this a bug?

[van_havn]

The monthly tweet cap usage applies to v2 endpoints. You posted your question under v1.1 so I’ll assume that answers your question.

Tweet consumption caps apply at the Project-level, effectively limiting the volume of Tweets you can retrieve from certain Twitter API v2 endpoints within a given month.

Tweet caps and Projects

[seeminglee]

Ah ok. Is there anyway to see the cap for v1? If not I guess I will run on v2 instead.

Thanks for your help!

[van_havn]

Honestly, I don’t think in terms of cap usage for v1.1; however, most, if not all, endpoints have rate limits:

Rate limits: Standard v1.1

Rate limits: Premium v1.1

v1.1 also has application/rate_limit_status.json

Twitter API v2 rate limits

Check out HTTP headers and response codes as well. Many 3rd party Twitter API libraries take advantage of HTTP headers and have rate limit management built-in.

[seeminglee]

Yes I know. I am mostly trying to see why I am rate limited on a search endpoint, and am hoping to find some ways to see usage similar to how I can do it via google api.

I know that I am supposed to know, but as I have several programs running that use the same endpoint, I was hoping for a graph of sorts.

[van_havn]

No graphs that I know of, sorry.

[IgorBrigadir]

I have several programs running that use the same endpoint

Calling an endpoint in parallel like this nearly always throws errors in my experience. It’s better to have a single “worker” on a single endpoint, that monitors the rate limit HTTP headers and waits appropriately, and have your own internal services call to your worker, not directly to twitter.

[seeminglee]

Thanks for the tip for better architecture!