#1

Hi!

Im developing a app that uses the following endpoints of the Twitter API v1.1:

  • POST statuses/update
  • POST statuses/retweet/:id

And the following endpoints of the Twitter API v2:

  • GET /2/users/:id
  • GET /2/tweets/:id

I have to post around 600 publications combining tweet and retweets from 600 different accounts in a 2h window. And I have seen in the docs that the limit is 300 request in a 3h window no matter tweet or retweet.

Im using user access token instead the app’s token.
So the question is, if Im using the user token to make this requests, could I reach the rate limit?

Or cause Im using the user token, I actually have 300 request per user.

And could I user the V2 lookup endpoints during these 600 publications or could be better to wait until these requests end.

Thanks for any help!

#2

Posting tweets is always using a user access token - so your limit for all posts, is 300 in 3 hours. You may hit other limits along the way - the rate limit is adaptive.

Also, if you have many accounts - by default you have 300 tweets in 3 hours for your entire app, no matter how many users you have.

It’s safe to use the GET requests in parallel while you’re calling other endpoints.

1 Like
#3

So in this case, it will hit the rate limits, right?

Is there anyway to achive these posts in the 2 hours window?

Thanks for your help!

#4

Yeah it will most likely hit a rate limit, probably sooner than the 300 in 3 hours if it looks “spammy”. There is no way to post more than the limit.

#5

What behaviours could be considered “spammy”?
And is there any best practices to avoid being “spammy”?

Thanks for your help!!

#6

I don’t know - I’m not Twitter so I’ve no special insight into the anti spam systems. This article lists some specifics though: Twitter's platform manipulation and spam policy | Twitter Help and there’s also the automation rules: Twitter's automation development rules | Twitter Help

#7

Thanks for all your help!
I have one more question, Im checking the GET application/rate_limit_status and it seems that only can check the rate-limit status for the GET endpoints and only for the app, am I right?

Is there anyway to check the current status of rate limit for the POST endpoints? So we can know how many more requests we can make before we hit the limit.

Thanks!!

#8

No, there’s no way to check POST rate limits exactly because they’re adaptive - some of the rate limits are: Understanding Twitter limits | Twitter Help (tweeting via API is 300 tweets in 3 hours though) others can be assumed to be 15 in a 15 minute window.

#9

Thanks @IgorBrigadir !!

You have been really helpfull!

:fire: :fire: :fire:

1 Like
#10

Hi!

I already reach the rate limit for the POST tweet/retweet endpoints.

I would like to ask, Now that I reach that limit and the request returns this message:

[{“code”:185,“message”:“User is over daily status update limit.”}]

The question is if my first post was at 10:00AM and I have reach the 300 rate limit within the 3 hours window, When could I POST again without any issues of rate limit?

I will have another 300 request at 13:00, or I will have one request when I reach the time of the first publication + 3 hours?

Or maybe Twitter has predefined time like 300 request 0:00 AM to 03:00 AM, 3:00 AM- 6:00 AM…

Thank for your help!

#11

I don’t know for certain, but as far as i can tell it’s not a fixed predefined time window, I think it’s more like a “sliding window” than a hard reset.

1 Like
#12

Ok! Thanks for your help Igor!

#13

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.