X (Twitter) Trends Scraper - 24-Hour Trend History

Disclaimer: This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by X Corp. or any of its subsidiaries. All trademarks mentioned are the property of their respective owners. "X (Twitter)" is referenced only to describe the publicly available website this Actor collects data from.

Scrape X (Twitter) trending topics for Worldwide and 58 countries - and not just what is trending right now. Every run can return the full 24-hour history, one snapshot per hour, so you can see when a hashtag entered the list, how high it climbed and when it fell out. Export to JSON, CSV or Excel.

No login, no API key, no paid X API tier.

Where the data comes from

This Actor reads the public trend pages of trends24.in, an independent site that archives X's own trend lists hour by hour. It does not call X's API and does not need an X account. Every row carries a source field so the provenance travels with your data. The hourly archive is the reason this Actor can give you history at all - X itself only publishes what is trending at this moment.

What you get

24-hour history	One snapshot per hour for the last 24 hours, each with its own UTC timestamp and hoursAgo - track a hashtag's whole run, not a single moment
59 places	Worldwide plus 58 countries. Every slug in the picker was checked against the live source, so nothing you can select comes back empty
Rank order	rank 1-50 exactly as X ordered the list at that hour
Hashtag flag	isHashtag separates #hashtags from plain keyword trends in one column
Search links	A ready X search URL per trend, so you can jump straight to the posts
Compact snapshots	Optional one-row-per-place-per-hour summary: trend count, hashtag count and share, and the top 10 names
Filters that cost nothing	Hashtags-only and name-contains are applied before billing - filtered rows are never charged
Monitor mode	Remembers what it has seen so a scheduled run returns only trends that are new

Use cases

• Catch a trend early - schedule it with Monitor mode and get only hashtags that have just entered a country's list.
• Measure a campaign - did your hashtag reach the list, in which countries, at what rank, and for how many hours?
• Compare markets - the same run covers 59 places, so you can see what is global and what is local.
• Newsroom monitoring - a 24-hour rank history is a timeline of when a story broke.
• LLM input - clean, ranked, timestamped topic lists per country, ready for clustering or summarisation.

How to use

1. Sign up for Apify - the free plan is enough to try this Actor.
2. Open the X (Twitter) Trends Scraper, pick your places (Worldwide plus any of 58 countries) and set hours back - 1 for what is trending right now, 24 for a full day of history.
3. Click Start and watch trends stream into the dataset table.
4. Export as JSON, CSV, Excel, XML or RSS - or pull results programmatically through the Apify API.

Input

Trending right now, worldwide:

{ "places": ["worldwide"], "hoursBack": 1 }

A full day of history for three markets:

{
  "places": ["united-states", "united-kingdom", "india"],
  "hoursBack": 24,
  "maxTrendsPerSnapshot": 50
}

Only hashtags, and only ones mentioning a keyword:

{ "places": ["brazil"], "hoursBack": 24, "hashtagsOnly": true, "containsText": "cup" }

A dashboard row per country per hour, without the individual trends:

{
  "places": ["worldwide", "japan", "nigeria"],
  "hoursBack": 24,
  "includeTrends": false,
  "includePlaceSnapshots": true
}

Output

A trend row:

{
  "type": "trend",
  "place": "united-states",
  "placeName": "United States",
  "placeUrl": "https://trends24.in/united-states/",
  "snapshotAt": "2026-09-07T07:00:11.468Z",
  "hoursAgo": 0,
  "rank": 1,
  "name": "#Lanterns",
  "isHashtag": true,
  "searchUrl": "https://twitter.com/search?q=%23Lanterns",
  "source": "trends24.in",
  "scrapedAt": "2026-09-07T07:17:12.500Z"
}

A placeSnapshot row (optional, one per place and hour):

{
  "type": "placeSnapshot",
  "place": "united-states",
  "placeName": "United States",
  "snapshotAt": "2026-09-07T07:00:11.468Z",
  "hoursAgo": 0,
  "trendCount": 50,
  "hashtagCount": 14,
  "hashtagSharePercent": 28,
  "topTrends": ["JUNGKOOK", "Louisville", "#Lanterns", "WHALIEN 52", "Mookie"],
  "source": "trends24.in"
}

Three dataset views ship with the Actor: Trends, Trend history and Place snapshots.

Good to know

• 59 places, every one of them live. X does not publish a trend list for every country, so the picker carries only the places that actually return trends - nothing you can select comes back empty.
• 24 hourly snapshots per place, up to 50 trends each - about 1,200 rows per place per run at full depth.
• No post-volume column. X no longer publishes a post count per trend, so this Actor ships no tweetVolume field rather than an always-empty one. Rank and time-on-list are the volume signals that are published.
• Snapshots are hourly, and timestamps are UTC. A trend that appeared and vanished inside one hour may not be in the archive.
• City-level trends are not covered - the picker is Worldwide plus countries.
• Trend names are whatever X published; some are in non-Latin scripts and are returned exactly as-is.

How much does it cost to scrape X (Twitter)?

This Actor uses Apify's pay-per-event pricing: you are charged only for the results it delivers, with no monthly rental and no start fee. The events it can charge are:

• Trend scraped - Charged once per trending topic written to your dataset - place, capture hour, rank, name, hashtag flag and the X search link. Trends removed by your filters, trends already seen in monitor mode, and places that could not be read are never charged.
• Place snapshot - Charged once per place and hour when snapshot rows are switched on - trend count, hashtag count and share, and the top 10 trend names in a single row. Turn off 'Include one row per place snapshot' to skip it entirely.

The current price of each event is shown on the Pricing tab of this page. Set a maximum total charge on the run if you want a hard cap on spend, and use the input limits to control how much the Actor fetches.

Automate & schedule

Run this Actor on autopilot and pull results into your own stack:

• Apify API - start runs, fetch datasets and manage schedules over REST.
• apify-client for JavaScript and apify-client for Python - official SDKs.
• Schedules - run it hourly, daily or weekly and keep your dataset current.
• Webhooks - trigger downstream actions (CRM import, Slack alert, email sequence) the moment a run finishes.

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'MY_APIFY_TOKEN' });

const run = await client.actor('scrapesage/x-trends-scraper').call({
    "places": [
        "worldwide",
        "united-states"
    ],
    "hoursBack": 24,
    "maxTrendsPerSnapshot": 50,
    "includePlaceSnapshots": false
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(`Got ${items.length} records`);

Integrate with any app

Connect the dataset to thousands of apps - no code required:

• Make - multi-step automation scenarios.
• Zapier - push new records straight into your CRM or spreadsheet.
• Slack - get notified when a scheduled run finds something new.
• Google Drive / Sheets - auto-export every run to a spreadsheet.
• Airbyte - pipe results into your data warehouse.
• GitHub - trigger runs from commits or releases.

Use with AI assistants (MCP)

The output is clean, LLM-ready JSON. You can call this Actor from Claude, ChatGPT or any agent framework through the Apify MCP server - describe the data you need and let the assistant run this Actor for you.

Agent-ready: autonomous payments (x402 & Skyfire)

This actor is agent-ready — AI agents can discover it, run it, and pay for it autonomously, with no Apify account and no human in the loop. It uses pay-per-event pricing and limited permissions, so it qualifies for Apify's agentic-payment standards:

• x402 — an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the Apify MCP server — no account, no API key.
• Skyfire — agent-to-service payments for fully autonomous AI-agent workflows.

Building an AI agent, MCP tool, or autonomous data pipeline? This scraper is ready to plug in and pay as it goes.

More scrapers from scrapesage

Related Actors in the same category:

• LinkedIn Ad Library Scraper - Competitor B2B Ads & Creatives
• Instagram Hashtag Scraper - Filtered Post Search
• Twitter (X) Scraper - Tweets, Profiles & Monitor
• LinkedIn Profile Scraper - People, Job Changes & B2B Leads
• People Search Scraper for LinkedIn - By Job Title

Tips

• One run, many markets. Every row carries place and placeName, so covering 59 places in one run beats 59 scheduled runs.
• Rank history is the story. Pull hoursBack: 24 and pivot on name + snapshotAt to plot exactly when a hashtag entered, peaked and dropped out.
• Campaign tracking. Combine hashtagsOnly with containsText to keep only your own tag, then check which countries it reached and at what rank.
• Dashboards without the noise. Set includeTrends: false and includePlaceSnapshots: true for one compact row per place per hour.
• Catch entries early with monitor mode on an hourly Schedule - you are charged only for trends that are new.

FAQ

How is this Actor billed? Pay-per-event: you pay only for the results it delivers, with no monthly rental and no start fee. The per-event price is shown on the Pricing tab.

Can I schedule it and get results automatically? Yes - create a Schedule and add a webhook or an integration (Google Sheets, Slack, Make, Zapier) to push each run's dataset wherever you need it.

Which export formats are available? Every run's dataset can be downloaded as JSON, CSV, Excel (XLSX), XML, HTML or RSS from the Apify Console or the API.

Can I run it from code or an AI agent? Yes - through the Apify API and client libraries, or from Claude, ChatGPT and other assistants via the Apify MCP server.

Is it legal to scrape X (Twitter)? This Actor collects publicly available data only. You are responsible for using the output in compliance with applicable laws (including data-protection law where personal data is involved) and the source's terms. See the Disclaimer below.

Is this an official X (Twitter) tool? No. It is an independent, third-party Actor with no affiliation to, endorsement by or sponsorship from X Corp. See the Disclaimer below.

Disclaimer

This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by X Corp. or any of its subsidiaries. All trademarks mentioned are the property of their respective owners.

"X (Twitter)" and any related marks are the property of their respective owners and are used here only in a descriptive, nominative sense - to identify the publicly accessible website from which this Actor collects data. This Actor is not an official X (Twitter) product, is not authorised or certified by X Corp., and does not distribute X (Twitter) software. It collects only publicly available information; you are responsible for ensuring your use of that data complies with applicable laws, regulations and the terms of the source website.

Need help?

Open an issue on the Actor's Issues tab, or visit the Apify help center. Feature requests are welcome - this Actor is actively maintained.