#1

I see that API v2 limits the number of blocks to 50 per 15 minutes, how many is the limit in API v1.1?
Also, apart from rate limiting, is there such a thing as too much blocking that can get an account locked?

#2

I think the v1.1 API doesn’t have a published limit, so it’s assumed to be 15 calls in 15 minutes, but in reality it’s “adaptive” or “bursty” so you can sometimes make a few more: Rate limits: Standard v1.1 | Docs | Twitter Developer Platform

Note that endpoints not listed in the chart default to 15 requests per allotted user. All request windows are 15 minutes in length.

2 Likes
#3

It’s also worth knowing that the POST / write operations like this also have account limits, so if an account is observed to take a large number of actions in a short period of time it might be unusual.

In general we would strongly recommend that you use v2 for new builds, unless an endpoint does not exist or there’s a compelling reason not to do so. Thanks!

1 Like
#4

I see, thank you very much.

#5

Thanks. I see, I just can’t create any more v2 apps because I have already published one “product” app using api v2.

（This text was translated by DeepL translation.）

#6

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