Repository navigation
There's an issue with account bans when using the official X API for developers. Has anyone encountered this lately? #213
Description
Hello, developers!
Recently, there have been many cases and discussions on various forums about X accounts being banned after using the official X pay-per-use API. Even with simple read requests (search, timelines), and with write actions like posts, likes, and retweets, the risks are even higher. Important: programmatic replies have recently been limited—now only if the author mentioned you or quoted the post (February 2026 anti-spam update). No spam—but suspension without explanation.
What's happening:
Read: GET search/timelines
- Write: POST tweets/likes/retweets (replies with restrictions)
- Rate limits are met, pure dev traffic
- Banned account - "suspended" without details
- Appeals often result in generic rejections
Thoughts: Most people simply post regular messages, and even automated posts are allowed by X's rules. Most likely, X's AI filters have become very sensitive to dev traffic after the new rules and updates, making using X's API for development quite risky. What if their AI has gotten out of control, gone berserk, or is simply blocking random accounts?
Questions:
- If endpoints for posts, likes, retweets, and comments are available in the API, why are they needed if accounts are banned for using them, even when tested as automated accounts?
- Has anyone encountered this recently?
- Were there any bans after reading/posting/liking/retweeting? If so, why are these endpoints needed?
- Which endpoints trigger most often?
- Were there any successful appeals?
- Do you agree that the filters are too strict for developers?
Share your experiences - let's figure it out together! 👇
X team: It would be great to clarify the exact triggers or introduce a whitelist for verified API keys.
#XAPI #Developers #Suspension #PayPerUse
Activity
kolyantrend commentedon Apr 12, 2026
jpjose632-del commentedon Aug 9, 2026
chungaperea5@gmail.com
jpjose632-del commentedon Aug 9, 2026
r17411n commentedon Sep 23, 2026
My account got suspended in a similar manner, whilst testing a Discord app using the X API, all it was doing was retrieving posts and from that point only retrieve the latest post by the X handles that are added to the App.
I think the issue was that I was also manually placing posts to then use as test data to retrieve with the API. After three of those posts, my account was instantly suspended, with paid credits remaining stuck on that particular account. Fun!
I don't think there is anyway I hit an API limit since I'm not out of credits. And shouldn't X rate limit traffic themselves?
I asked for a review of my suspension, but it did not matter at all. Now I'm just afraid to put credits or PPU + a payment method on a different account; since there will be a good chance the same thing will happen again.