#1

Hello.
We developed an application using Twitter API v 1.1
Some time ago we faced “User is over daily status update limit” errors as reply for “statuses/update” request.
Search the Forum revealed that requests fail because the application-level POST limits.
The Elevated access was requested and granted to Developers account.
The application was connected to project and the project also is elevated.
But the error still appears.
Application ID is 12905283.

What should we do to apply elevated application-level limits to API v 1.1 “statuses/update” endpoint?

#2

Do we need to use API v2 endpoint to be limited by elevated rates, or is there any way to apply elevated access to API v1.1 endpoint?

#3

The posting limit for API v1.1 and v2 is the same, which is 300 per 3 hours, including post retweets

https://developer.twitter.com/en/docs/twitter-api/rate-limits#v2-limits

https://developer.twitter.com/en/docs/twitter-api/v1/rate-limits

2 Likes
#4

We do have an elevated access which increases the limit up to 200 tweets per 15 mins.
But in the documentation only API v2 endpoints mentioned.

Elevated limits screenshot
Elevated limits screenshot1654×1038 52.2 KB

Thank you for the links - there are differences between v1.1 and v2 limits.
The v2 limits page mentions 15 min window for manage tweets " POST /2/tweets", while the v1.1 does not mention it for " POST statuses/update".

The information popup on the screenshot says that “Rate limits are the number of requests (or API calls) that are allowed. App limits apply only to a single App, while user limits apply to a combination of all Apps.”

#5

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