Today we began enforcing new default app-level rate limits for common POST endpoints.
As a reminder, in July we announced changes to increase accountability on our developer platform and reduce the distribution of spam through our APIs.
Beginning today, the new POST endpoints rate limits are:
In practice, a small minority of developers surpass these limits today so most developers will not be impacted.
If you hit rate limits beginning today, you can apply for free, elevated access by following these steps:
- Make sure you have applied for a developer account â start your application if you havenât.
- Complete a request for elevated POST access with the steps below.
Request for elevated POST access
For each app that needs elevated POST access:
- Make sure how the app is used is described in the app details. You can see and edit that field from the Apps page.
- Submit an elevation request on our API Policy Support Form:
A. Select âI would like to apply for elevated POST limits.â
If you do not see this option, you are not currently posting at a rate that would require an elevation.
B. Submit the app details and a short description of your use case
Once you have completed all of the above, we will review your elevation request along with your developer account application if it has not yet been reviewed. We may need to request additional information, so please monitor the email address associated with your account. We will notify you when your app has elevated POST access.
We recognize that these required steps are inconvenient. Due to the wide array of developers and apps that use our standard APIs to post content to Twitter, we are adopting processes to ensure more accountability across developers that post content. We appreciate your part in helping us prevent spam on our platform.
Regards,
The Twitter Developer team