This changelog highlights releases that materially changed Twitter/X Trends Scraper for users. Dates use UTC; small internal refactors and routine maintenance are intentionally omitted.
Reliability
- Fewer failed runs from network trouble: when Apify Proxy can't reach X (status 594, connection refused), the request now retries through another proxy connection instead of failing the run, and retries on the same proxy group use a fresh connection. Runs also no longer stall at startup if a platform call hangs.
Reliability
- Clearer message when a place has no trends: X only publishes trends for 467 listed places, so codes like
CZ or smaller cities outside the list end with a status that says so. The README now states which countries are covered.
Reliability
- Place names now match without regard to case, accents or punctuation, and common local names work:
Ciudad de Mexico and CDMX give Mexico City, München gives Munich. Before, such runs found no location.
- A request that stalls now gives up after 15 seconds and retries through another proxy, instead of using up the whole run timeout.
Features
- Added
locationCount, locationsTrendingIn, and bestRank to every trend so multi-location runs show shared topics without extra aggregation.
Reliability
- Improved proxy fallback so trend requests can recover from temporary X/Twitter access blocks instead of returning empty results.
Changes
- Country-code inputs now resolve against current Twitter location data, helping return trends for the requested country.
- Updated the default trends limit to 20 per location for a more economical starter run.
Features
- Initial release for extracting real-time Twitter/X trends by country or city, including trend volume and hashtag data.
