Reminder: In July, we announced that we are making changes to increase accountability on our developer platform and reduce the distribution of spam through our APIs. We will be enforcing new default app-level rate limits for common POST endpoints on October 22nd.
At that time, the new POST endpoints rate limits will be:
- Tweets & Retweets (combined): 300 per 3 hours
- Likes : 1000 per 24 hours
- Follows : 1000 per 24 hours
- Direct Messages : 15,000 per 24 hours
In practice, a small minority of developers surpass these limits today so most developers do not need to take any action on this.
If you need to take action on this, you will have received an email notification from us. Please make sure that:
- You have applied for a developer account — start your application if you haven’t.
- You 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
Note: if you have not been invited to apply for elevated POST access, you will not see this option on the API Policy Support form. If you still believe you need access, please select ‘I have an API policy question not covered by these points’ and explain why you may need elevated POST access.
Please complete all steps above by October 17th to receive elevated POST access.
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.
The Twitter Developer team