Twitter / X Trends Scraper – Trending Topics & Hashtags
Pricing
from $10.00 / 1,000 results
Twitter / X Trends Scraper – Trending Topics & Hashtags
Twitter / X trends scraper: trending topics and hashtags on X for 60+ countries or worldwide, right now or for any hour in the past 24 hours. Batch many countries in one run, schedule hourly to build a trend history. No X API key. Export to CSV, JSON, Excel or API.
Pricing
from $10.00 / 1,000 results
Rating
0.0
(0)
Developer
Maged
Maintained by CommunityActor stats
2
Bookmarked
37
Total users
5
Monthly active users
11 hours ago
Last modified
Categories
Features
Share
What does Twitter / X Trends Scraper do?
Twitter / X Trends Scraper gets the trending topics and hashtags on X (Twitter) for worldwide or any of 60+ countries, right now or for any hour in the past 24 hours. One row per trend, ranked, with the country and hour it came from.
No X developer account, no paid API plan. It runs on Apify, so you can schedule it every hour, call it from the API, or send the trends to Google Sheets, Slack, Make, Zapier or n8n.
What people use it for
- Content planning: see what's trending in your market before you post, and jump on a topic while it's still rising.
- Trend history: X only shows trends live. Run this hourly and you build your own archive of what trended where and when.
- Social listening and brand alerts: get notified when your brand, product or competitor shows up in a country's trends.
- Comparing countries: run 10 countries at once and spot a topic that's spreading from one market to the next.
- News and research: a timestamped record of what people were talking about during an event.
- Hashtag research: find the trending hashtags to use in a given country today.
Why use this one?
- No X API: no developer approval, no $100+ a month API plan.
- 60+ countries plus worldwide, all in one run with batch mode.
- The past 24 hours, by the hour: missed a spike this morning? Pick the hour (UTC) and get the trends from then.
- Flat, ranked rows: ready for CSV, Excel or a database without cleanup.
- You only pay for trends: a query that fails isn't saved as a row or charged. It shows up in the run's status message instead.
How to use it
- Click Try for free.
- Pick a country, or leave it empty for worldwide.
- Optionally set an hour (UTC) to see what was trending earlier.
- Click Start. The ranked trends appear in the Output tab.
- Download as JSON, CSV or Excel, or set a schedule (hourly works well).
Input
One country:
{"country": "united-states","limit": 20}
Several countries or hours in one run:
{"queries": [{ "country": "united-states" },{ "country": "united-kingdom", "hour": 9 },{ "country": "japan" }],"limit": 20}
| Field | Type | Description | Default |
|---|---|---|---|
country | string | Country slug, like united-states, united-kingdom, japan, saudi-arabia. Empty = worldwide | worldwide |
date | string | today, or a past date YYYY-MM-DD (see the note below) | today |
hour | integer | Hour in UTC (0–23). With today, gets the trends from that hour within the past 24 hours | now |
limit | integer | Trends per query (10–50) | 50 |
queries | array | Batch mode: a list of {country, date, hour, limit} objects. A query without its own limit uses the top-level one | — |
About past dates: older days come from the source's archive, which has been unreliable lately. When it's down, those queries fail and are listed in the status message (not charged). Today and the past 24 hours work normally.
Output
One row per trend, ranked:
{"position": 1,"trend": "#WorldKindnessDay","tweets": null,"country": "united-states","date": "today","hour": null,"limit": 20,"scraped_at": "2026-11-13T09:00:05Z","success": true,"query": "country=united-states&date=today&limit=20"}
| Field | Type | Description |
|---|---|---|
position | number | Rank in the trending list |
trend | string | Trend name or hashtag |
tweets | string | Post volume when the source shows it. X stopped publishing most of these counts, so it's usually empty |
country, date, hour, limit | The query this row came from | |
success | boolean | Always true on saved rows |
query, scraped_at | string | Query summary and collection time (UTC) |
How many results will I get?
You pay per trend, so the bill follows the number of rows. Your plan's rates are on the Pricing tab.
| Input | Results |
|---|---|
| 1 country, limit 50 | Up to 50 rows |
| 1 country, limit 10 | Up to 10 rows |
| 10 countries, limit 20 | Up to 200 rows |
| 1 country every hour for a day, limit 10 | Up to 240 rows |
Tips
- For an hourly archive, keep limit at 10–20. The top of the list is what matters, and it keeps a 24-runs-a-day schedule cheap.
- Use Apify webhooks or the Slack integration to get pinged when a keyword enters the list.
- Want to know what people are actually searching for, not just posting? Pair it with Google Trends Scraper below.
FAQ
Do I need an X account or API key? No. It reads public trending lists, nothing behind a login.
How often do trends change? All the time. The list moves within minutes during big events, which is why the hour option and hourly schedules are useful.
Can I get trends for a city? Not right now, countries and worldwide only.
Why is tweets empty?
X no longer shows post counts for most trends, so there's usually nothing to read.
Is it maintained? Yes, I keep it running. If something breaks, open an issue in the Issues tab and I'll look at it.
Need a custom feature? Open an issue or message me on Discord: maged03211
⭐ Found it useful? A short review on the Store helps other people find it, and it tells me what to improve next.