Twint is archived: the Twitter scraper that stopped working
Twint is archived and no longer receives fixes. See what it did, why it broke, and the maintained routes for X data today.
Short answer
Twint's archived Twitter scraper stopped working because X closed the unauthenticated access patterns it relied on. Replace it with the paid X API or a maintained hosted public-data tool for collecting posts and profiles.
Status checked 2026-11-12. Routes that work for X (Twitter) data
The official route first, then the catalogue Actors that fit this problem (posts and profiles), by their published fields. Store figures are the publisher's public numbers.
Official price: Charged per resource returned: $0.005 per Post, $0.010 per User. Owned Reads on qualifying own-account endpoints are $0.001 per resource. A 3 million Post-read monthly cap applies to self-serve pay-per-use. Compare all 20 X (Twitter) routes.
What is verified
| Fact | Value |
|---|
| Repository | Archived on GitHub |
| Method | Twitter scraping without the official API |
| Why it broke | X closed the unauthenticated access patterns Twint relied on |
| Current route | Paid X API or a maintained hosted public-data tool |
Why the old collection method failed
Twint scraped Twitter without the official API. X closed the unauthenticated access patterns behind that method, removing the route its requests depended on.
The Twint repository is archived and no longer receives fixes. Reinstalling the archived project leaves the underlying access restriction in place.
Move the task to a maintained route
Choose between the paid official X API and a maintained hosted public-data tool according to the posts and profiles you need. Consult the official X documentation when assessing API access.
Compare the replacement's output with what your analysis consumes before changing downstream code. Check search behavior and content coverage rather than assuming a replacement accepts Twint's options.
What works now
A maintained hosted public-data tool or the paid official X API is the current route for replacing Twint collection. Verify post and profile retrieval against the task your old script performed, then adapt the analysis to the replacement's output.
Questions people ask
Is Twint still maintained?
The GitHub repository is archived and no longer receives fixes. Use a maintained collection route for new X work.
Why did Twint stop collecting posts?
X closed the unauthenticated access patterns Twint used. Its archived scraping method therefore cannot serve as a dependable route for ongoing collection.
Will reinstalling Twint solve the problem?
Reinstalling the archived code leaves X's access restrictions unchanged. Move the collection task to the paid X API or a maintained hosted public-data tool.
Can an existing Twint script be reused?
Its search requirements and analysis logic can guide a migration. Check the replacement's inputs and output before adapting the script, since compatibility needs verification.
Sources
Every dated claim on this page comes from the public sources below. Check the source before you make a business decision on it.
Content updated 2026-11-12Data checked 2026-11-12