X (Twitter) Trends Scraper - Trending Topics by Country & City
Pricing
from $0.09 / 1,000 trends
X (Twitter) Trends Scraper - Trending Topics by Country & City
Scrape X (Twitter) trending topics and hashtags for 467 places: worldwide, 62 countries, 400+ cities. The current top 50, the hourly timeline, rank change, history by date and hour, top lists. No X account, no login, no cookies. $0.09 per 1,000 trends.
Pricing
from $0.09 / 1,000 trends
Rating
0.0
(0)
Developer
Top Api
Maintained by CommunityActor stats
0
Bookmarked
3
Total users
2
Monthly active users
10 days ago
Last modified
Categories
Features
Share
What does X (Twitter) Trends Scraper do?
X (Twitter) Trends Scraper collects the trending topics and hashtags on X for any of the 467 places X publishes trends for: worldwide, 62 countries and 400+ cities. Each trend comes back as one row with its rank, its X search link, its place (with WOEID and country code) and the time of the list. Every row also says how the trend is moving: its rank in the list before, whether it is new, its best rank and how many hours it has been trending, and in which of your other places it trends too. The lists are read from the two public X trend trackers, trends24.in and getdaytrends.com, and every row names the site it came from (source, sourceUrl).
Also known as: Twitter trends API · X trending topics scraper · trending hashtags by country · Twitter trends by city · WOEID trends · trends24 scraper · getdaytrends scraper
- The list now, the hourly timeline or a past date: the current top 50, every hourly list of about the last 20 hours, picked periods (1, 3, 6, 12, 24 hours, 2 and 3 days ago), N hours ago, or any hour of a past day for worldwide back to 2024-05-15.
- Rank movement on every row:
previousRank,rankChange,isNew,bestRank24h,hoursTrending24h,firstSeenAtand the fullrankHistory. - Spread across places:
locationCount,locationsTrendingInandbestRankAcrossLocationsover the places of your run. - Every place in one run: type
all,all countries,all citiesorall in Japan. - Top lists: longest trending and most tweeted, for the day, the week or the month.
- Trend records (add-on): a trend's best rank ever and when, and the places it trends in now and before.
- Monitor mode for hourly schedules: only trends not delivered for that place in the last 24 hours (
monitorWindowHours). - No X account, no login, no cookies, no API key: the actor reads only trends24.in and getdaytrends.com, never X itself.
What data can you get from X trends?
| 🔢 Rank (`rank`) | 🏷️ Trend text (`name`), hashtag / cashtag / phrase | 🔗 X search link (`url`, `query`) |
| 🌍 Place, country, country code | 🗺️ WOEID and parent WOEID | 🏙️ Place type (worldwide, country, town) |
| 🕒 List time (`snapshotAt`), age (`hoursAgo`) | ⬆️ Rank before, change, new flag | 🏆 Best rank, hours trending, first / last seen |
| 📈 Rank history, list by list | 📍 Places it trends in, best rank there | 💬 Post count (history before Jan 2026) |
| ⏳ Longest trending (total hours) | 🔥 Most tweeted (score) | 📚 Trend record: best rank ever + places |
Measured on a run over all 467 places (2026-11-06): 21,937 trends from 448 places (19 towns had no list that hour). Rank, name, query, link, trend type, place, WOEID, list time, best rank, hours trending, first and last seen, rank history and spread across places were filled on 100% of rows; country and country code on 99% (worldwide has none); previousRank and rankChange on 87% (the other 13% are trends that were new to the list, isNew: true).
How to scrape X trends with X (Twitter) Trends Scraper
- Create a free Apify account. It comes with $5 of monthly credit and no card is needed.
- Open X (Twitter) Trends Scraper and click Try for free.
- Type the places into Places:
United States,New York, US,JP,23424977,worldwideorall. - Pick the hours you want under Which hours (empty = the list now) and the filters you need.
- Click Start. The current lists of the United States and worldwide (100 trends) took 2-5 seconds on our test runs.
- Open the Storage tab and Export as JSON, CSV or Excel, or connect a schedule.
⬇️ Input
| Parameter | Type | Description |
|---|---|---|
| 🔍 What to scrape | ||
locations | array | Places, one per line: country or town names, Town, Country, two-letter codes, WOEIDs, trends24 / getdaytrends links, or all / all countries / all cities / all in <country>. Empty = worldwide and the United States. |
woeids | array | Yahoo Where On Earth IDs, as X uses them (1 = worldwide, 23424977 = United States). |
listLocations | boolean | Return the 467 places instead of trends. Default false. |
listCountry / listPlaceType / nameContains | string | Filter the place list by country, type (country, town, worldwide) or name. |
| 🎯 Which hours | ||
includeHistory | boolean | Every hourly list trends24 keeps for the place (about 20 lists, ~1,000 rows a place). Default false. |
timePeriods | array | live, 1h, 3h, 6h, 12h, 24h, 2d, 3d. |
hoursAgo | integer | The one list from N hours ago (0-23). |
date + hour | string + integer | A past day (UTC), with an hour for one list or without for all 24. Also yesterday, 3 days ago. |
from / to / every | string | A range of lists, one per step (1h, 6h, 1d). |
queries | array | Many lookups in one run: [{"location": "worldwide", "date": "2025-01-01", "hour": 12}]. |
| ✂️ Refine results | ||
maxTrendsPerLocation | integer | Top N of each list, 1-50. Default 50. |
excludeHashtags / onlyHashtags | boolean | Drop #hashtags, or keep only them. |
includeKeywords / excludeKeywords | array | Keep trends containing one of these words, or drop them. |
dedupeTrends | boolean | With several lists: one row per trend per place (the newest). |
readAllTowns | boolean | With keyword or hashtag filters, towns are skipped when their country's own list has no match. Turn on to read every town. Default false. |
| ➕ Extra data | ||
trendDetails | boolean | The trend record add-on, $0.001 per trend name. Default false. |
maxTrendDetails | integer | Cap on trend records per run. Default 50. |
topLists | array | longest-day, longest-week, longest-month, tweeted-day, tweeted-week, tweeted-month (countries and worldwide). |
| 🔁 Monitoring | ||
monitorMode | boolean | Only trends not delivered for that place by earlier runs. Default false. |
monitorWindowHours | integer | A trend delivered within this many hours is not delivered again. Default 24. |
monitorStoreName / resetMonitor | string / boolean | The store that remembers deliveries; start over. |
| 📦 Output | ||
maxItems | integer | Cap on rows for the whole run. Empty = no cap. |
constantFields | object | Columns added to every row, e.g. {"campaign": "q4"}. |
| ⚙️ Advanced | ||
proxyConfiguration | object | Not needed normally (see Limits). |
maxConcurrency | integer | Pages read at once. Default 6. |
Field names of other trends actors are accepted as well, so an existing input pastes as it is: country (a name, code or the numbers 1-35 of the karamelo form), live / hour1 / hour3 / hour6 / hour12 / hour24 / day2 / day3, maxItemsPerTarget, getAvailableLocations, placeSearchTerms, at, maxResults.
Input JSON
{"locations": ["United States", "New York, US", "worldwide"],"timePeriods": ["live", "6h", "24h"],"maxTrendsPerLocation": 20,"excludeHashtags": false}
Write the town with its country when the name is shared
Valencia is a town in Spain and in Venezuela; the run takes the first and says so in the log. Write Valencia, Venezuela or Valencia, VE to pick one. all in Brazil returns Brazil and its 15 towns.
Pick the source of the hours you need
The current list and the hourly lists of about the last 20 hours come from trends24 for every place, towns included. Older hours come from getdaytrends: countries for the last 23 hours, worldwide by date back to 2024-05-15. getdaytrends does not serve a country's dated history right now (its own server answers HTTP 520), so those hours are named in the run status and log and never charged.
⬆️ Output
One row per trend in one list of one place:
{"type": "trend","rank": 4,"name": "Derrick Henry","url": "https://x.com/search?q=Derrick%20Henry","trendType": "phrase","location": "United States","woeid": 23424977,"countryCode": "US","placeType": "Country","snapshotAt": "2026-11-06T05:03:40.939Z","previousRank": 5,"rankChange": 1,"isNew": false,"bestRank24h": 4,"hoursTrending24h": 5,"firstSeenAt": "2026-11-06T01:36:23.087Z","rankHistory": [null, null, 7, 6, 5, 5, 4],"locationCount": 2,"locationsTrendingIn": ["United States", "Worldwide"],"source": "trends24.in"}
(A real row from the prefill run, shortened: rankHistory holds one value per list, 19 on that run.)
A trend record (add-on) sits in details on the first row of each trend name:
"details": {"allTimeBestRank": 1,"allTimeBestRankAt": "2026-10-12T04:00:00.000Z","worldwideRankNow": 2,"placesSeenIn": 26,"trendingNowIn": [{"location": "United States", "rank": 1}, {"location": "Mexico", "rank": 11}],"seenBeforeIn": [{"location": "Nigeria", "lastSeen": "6 hours ago"}]}
Fields
| Field | Meaning |
|---|---|
type | trend, topTrend (a top-list entry) or location (list mode) |
rank | Position in the list, 1-50 |
name, query, url | The trend, its X search query and search link |
trendType, isHashtag, isCashtag | hashtag, cashtag or phrase |
tweetVolume, tweetVolumeText | The post count, where the list carried one: X stopped publishing it in January 2026, so it is on history lists before then (13 of 50 trends on the worldwide list of 2025-01-01 12:00) and null since |
location, locationSlug, woeid, parentWoeid, country, countryCode, placeType | The place |
snapshotAt, hoursAgo, timePeriod | When the list was captured, its age, the period you asked for |
previousRank, rankChange, isNew | Rank in the list before (about an hour earlier), the change, new to the list |
bestRank24h, hoursTrending24h, firstSeenAt, lastSeenAt | Over the lists trends24 keeps for the place (about the last 17-20 hours) |
rankHistory, rankHistoryLists | Rank in each of those lists, oldest first; getdaytrends rows: the last 8 hours |
locationCount, locationsTrendingIn, bestRankAcrossLocations | Where else in your run the trend is in the latest list |
details, detailsCharged | The trend record add-on |
monitorStatus | Monitor mode: new, or details for a trend delivered earlier without its trend record and delivered again with it |
topList, period, totalDurationHours, score, lastSeen | Top-list rows |
trends24Url, getdaytrendsUrl, historyByDate | Place rows |
source, sourceUrl, scrapedAt | Where and when the row was read |
How can I use X trends data?
- 📰 Newsrooms: see what breaks in a country or a city before it reaches the wires, with
isNewandrankChange. - 📣 Social media and brand teams: join trends while they climb, and follow them across markets with
locationsTrendingIn. - 📊 Analysts and researchers: build an hourly archive by place, or pull worldwide history by date.
- 🤖 AI agents and content tools: feed today's trends into writing, ad or alert pipelines through the API or MCP.
- 💹 Traders: watch $cashtags trending by country.
How much does it cost to scrape X trends?
X (Twitter) Trends Scraper charges $0.09 per 1,000 trends ($0.00009 each). Place rows (list mode) cost the same. The trend record add-on is $0.001 per trend name. There is no start fee and no monthly rent. Filtered trends, duplicates, trends already delivered in monitor mode, and hours or places the trackers do not serve are not charged.
| Run | Rows | Charge |
|---|---|---|
| One place now | 50 | $0.0045 |
| The United States and worldwide now (the prefill) | 100 | $0.009 |
| One place, every hourly list (~20 lists) | ~1,000 | ~$0.09 |
| All 467 places now | ~22,000 | ~$1.98 |
| The 467 places as rows | 467 | $0.042 |
| 50 trends with their trend records | 50 + 50 | $0.0545 |
Platform usage is included in the price. Set a maximum charge on the run to cap the cost: the actor stops at it.
Integrations, API, scheduling & MCP
X (Twitter) Trends Scraper works with the Apify API, the Apify Python and JavaScript clients, Make, Zapier, n8n, Google Sheets, Slack, webhooks and the Apify MCP server for AI agents.
Run it on a schedule
Turn on Only new trends (monitor), name the store, and add an Apify schedule every hour. Each run returns only the trends that are new to each place's list; a run with nothing new returns 0 rows and charges nothing.
{"locations": ["United States", "United Kingdom", "India"],"monitorMode": true,"monitorStoreName": "trends-hourly","monitorWindowHours": 24}
More social media scrapers
- X (Twitter) Profile Scraper: followers, bio and verified badge of the accounts behind a trend.
- Bluesky Scraper: posts and profiles from Bluesky.
- TikTok Scraper: videos, hashtags and profiles from TikTok.
- Instagram Scraper: posts and profiles from Instagram.
- Google Trends Trending Now Scraper: what people search for, by country.
All our actors: apify.com/TopApi.
Limits & empty runs
- Lists are about an hour apart. trends24 captures X's list about every 52 minutes, so the current list can be up to an hour old. It keeps about the last 17-20 hours, around 20 lists a place.
- Older hours: countries for the last 23 hours and worldwide by date back to 2024-05-15 (getdaytrends). Towns have no history older than trends24 keeps.
- Post counts: X removed them in January 2026; live lists have none.
- WOEIDs come from Yahoo's public GeoPlanet data (CC BY 3.0). 17 of the 404 towns have no clear public WOEID and carry none: ask for them by name.
- Places without a list: X sometimes publishes no list for a town (19 of 467 on our all-places run). Those are named in the run status and log, not charged.
- Speed: all 467 places took 316-457 seconds on three test runs at the default 256 MB (about 80 seconds reading, the rest writing ~22,000 rows). The run uses the platform's own connection first and moves to an Apify datacenter proxy if a site refuses it. Residential is the last step and was never needed in our tests.
- Keyword and hashtag filters over many places: worldwide and the countries are read first, then the towns. A country's towns are skipped when the country's own list has no match (turn on Read every town to read them). A filtered run reads more places only while what it delivers pays for reading them: once its platform cost passes $0.0003 and 30% of what it has billed, the places left are not read and the status says how many. Ask for fewer places per run to get them.
- If every route is refused, the run ends FAILED with the reason and charges nothing. A run that matches nothing ends with a status that says what to change.
FAQ
How many trends can X (Twitter) Trends Scraper collect in one run?
Up to 50 per list. One place with every hourly list is about 1,000 rows (1,050 for Japan, 3 seconds). All 467 places now is about 22,000 rows (5 to 8 minutes on our test runs). Ranges of past hours add 50 per hour.
Can X (Twitter) Trends Scraper get trends for a city?
Yes. 404 towns have their own lists, e.g. New York, US, London, Tokyo or São Paulo. Turn on List the places for all of them with their WOEIDs (450 of the 467 places have a public one).
Can I get historical X trends?
Yes. Each place's hourly lists of about the last 20 hours, countries for the last 23 hours, and worldwide for any hour back to 2024-05-15 with Date and Hour, or From / To / Every for a range.
Does X (Twitter) Trends Scraper show tweet volume?
Only on history from before January 2026, when X still published post counts. Since then X shows none on its lists and the field is null.
Can I schedule X (Twitter) Trends Scraper to track trends every hour?
Yes. Use monitor mode with an hourly Apify schedule: each run returns only the trends that are new to each place.
Do I need an X account, cookies or an API key?
No. X (Twitter) Trends Scraper reads the public trend trackers trends24.in and getdaytrends.com. Nothing to log in to.
Can I use X (Twitter) Trends Scraper with the Apify API or an MCP server?
Yes. Call it from the API or the Python or JavaScript client. You can also connect the Apify MCP server to Claude, ChatGPT or Cursor and ask for "trending topics in Japan" in plain words.
Why did my X (Twitter) Trends Scraper run return no results?
Check the status message. It says whether a place was not recognised, whether the filters removed everything, whether monitor mode found nothing new, or whether the hours you asked for are not served.
Your feedback
Found a bug or need a field? Open an issue in the Issues tab and we will look at it.