X (Twitter) Trends Scraper (Trends by Country & City)

What is X (Twitter) Trends Scraper?

X (Twitter) Trends Scraper collects the trending topics on X by country or city, from trends24.in. For each location you get the ranked trends of the latest hourly snapshot, or of the last several snapshots of the past 24 hours, with the snapshot time and a link to the search on X. No X login or API key is needed.

Why use X (Twitter) Trends Scraper?

• Trend rank and name for any country or city, hour by hour over the last 24 hours.
• A search link for every trend, to check the conversation on X.
• Several locations in one run, for comparison across countries.
• Pay only for trends saved.

How to use X (Twitter) Trends Scraper

1. Enter locations as trends24.in paths: a country (united-states, turkey, united-kingdom) or a city (united-states/new-york, united-kingdom/london). Full trends24 URLs also work.
2. Set how many hourly snapshots to collect (1 = the latest only, up to 24).
3. Set how many trends per snapshot (up to 50).
4. Run it and download the dataset as JSON, CSV, Excel or HTML, or read it through the API.

Example input

{
    "locations": ["united-states", "turkey"],
    "snapshots": 1,
    "maxTrendsPerSnapshot": 50
}

Example output

A real row from a run on 2026-10-23 (united-states, latest snapshot):

{
    "source": "trends24",
    "location": "united-states",
    "locationName": "United States",
    "snapshotAt": "2026-10-23T01:16:06.996Z",
    "snapshotIndex": 0,
    "rank": 1,
    "trend": "Cavs",
    "trendUrl": "https://twitter.com/search?q=Cavs",
    "url": "https://trends24.in/united-states/",
    "position": 1
}

Data table

Field	Meaning
location, locationName	trends24.in path and the name shown on the page
snapshotAt	time of the hourly snapshot (UTC)
snapshotIndex	0 = newest snapshot, 1 = the one before, and so on
rank	position in that snapshot (1 = top)
trend	trend name as shown on the page
trendUrl	search link on X for the trend
url	trends24.in page the row came from

Tweet volumes are not returned. The trends24.in page does not show them in its HTML, so the Actor does not fill that field.

Input parameters

• Locations: trends24.in country or city paths, or full URLs.
• Snapshots (hours): 1 to 24, newest first.
• Max trends per snapshot: 1 to 50, in rank order.
• Proxy configuration: keep the RESIDENTIAL group. trends24.in blocks datacenter IPs (HTTP 403).

Pricing

Pay per trend row saved (see the Actor page for the current price). The run stops before it would exceed your max total charge.

X (Twitter) Trends Scraper vs. the X API

The X API needs a developer account and API keys. This Actor reads the public trends24.in pages instead, so it needs no X account. It only covers what trends24.in publishes: trend names, rank, time and location. It does not include tweets, users or tweet volumes.

Using X (Twitter) Trends Scraper with AI agents and MCP

Use it from the Apify MCP server or the API with a location path. Pay-per-event pricing is charged per row, so an agent that sets a maxTotalChargeUsd never goes over that budget.

FAQ

Why are there no tweet counts? The trends24.in page does not contain them in the HTML this Actor reads, so they are left out rather than estimated.

Why does a snapshot have fewer than 50 trends? trends24.in sometimes lists fewer trends for an hour. The Actor returns what the page shows.

Why does the run need a residential proxy? trends24.in returned HTTP 403 for datacenter requests during testing (2026-10-23). The residential route returned the pages.

Support and feedback

If you find a problem, open an issue in the Actor's Issues tab. A review helps other users find it.