X (Twitter) Trends Scraper by Country & City

Find current X (Twitter) trending topics and hashtags by country, city, or worldwide. Choose locations from the dropdowns and get one Dataset row per topic, including its rank, X search link, and the time X generated the trend list. No X login, API key, cookies, or proxy setup is required.

Compare regions, find timely ideas for local reporting or content planning, and schedule repeat runs to build your own trend history. This Actor collects current snapshots; it does not retrieve past trends or posts behind a topic.

What you get

• Up to 50 ranked topics for each selected location, with separate country and city lists.
• A direct X search link and source snapshot time for every topic.
• Exportable Dataset rows for spreadsheets, dashboards, API workflows, or scheduled reports.

X supplies post volume only when available. The Actor leaves missing counts as null rather than inventing an estimate.

How to use

1. Select one or more countries, cities, or both from the dropdowns. Leave both empty to get Worldwide trends.
2. Keep the default maximum of 50 topics per location, or lower it if you need fewer rows.
3. Run the Actor and open its Dataset. Export the results in the format you need or use them through the Apify API.

The country and city selectors are independent: choosing the United States does not automatically choose New York. Each selected location has its own list and up to 50 results. The Actor checks X's current location list when it runs; a location that X no longer supports may return no data.

Input example

The form and API input both use readable location names. City names include their country to distinguish places with the same name:

{
  "countries": ["United States (US)"],
  "cities": ["New York — United States (US)"],
  "maxTrendsPerLocation": 50
}

This example selects the United States and New York. With the default maximum, it can produce up to 100 Dataset rows.

Output example

Each row represents one trend at one location. This example is based on a real X response; topic names and positions change over time.

{
  "location_name": "United States",
  "location_woeid": 23424977,
  "location_type": "Country",
  "country_code": "US",
  "position": 1,
  "trend_name": "#ADifferentWorld",
  "trend_url": "http://twitter.com/search?q=%23ADifferentWorld",
  "trend_query": "%23ADifferentWorld",
  "tweet_volume": null,
  "as_of": "2026-09-24T08:51:56Z"
}

position is derived from X's result order, not supplied as a separate X field. as_of is when X generated that location's trend list (UTC), not the time when an individual topic first appeared. X does not always provide tweet_volume; a null value means no count was supplied, not zero posts. The Actor does not estimate missing counts.

Pricing

Billing is per successful location, not per topic row. One location with results triggers one trend-location-snapshot event, whether it returns 5 or 50 topics. The current price is $0.0015 per location on Free/Bronze, $0.0012 on Silver, and $0.0010 on Gold or higher. At the default 512 MB memory, a separate $0.00005 Actor-start event applies per run. For example, the United States and New York together incur $0.00305 in event charges on Free/Bronze when both return trends. Empty or failed locations do not trigger a snapshot event, but the start event still applies. Check the Pricing tab for current rates and whether platform usage is billed separately before a large run.

Freshness and limitations

Each run returns a current X snapshot. There is no past-date input. To build a history, schedule regular runs on Apify and retain their Datasets. as_of is X's snapshot time in UTC, not the moment an individual topic first appeared. Topic names, positions, and available locations can change between runs.

If one location cannot be fetched, the Actor continues with the others and records the problem in the run's FAILURES key-value record. The run fails if every selected location fails.

FAQ and support

Why is tweet_volume null?

X did not provide a count for that trend. null does not mean zero posts.

Can I get trends from a previous date?

No. This Actor only fetches the current list. Schedule it to collect future snapshots over time.

Does this Actor collect the posts behind each trend?

No. It returns trend names and X search links, not the matching posts. For help with a failed run, include the run ID in the Actor's Issues tab; do not post account credentials.

Related X tools

For account research, try X People Search. For the details and media of a known post URL, use X Media Downloader.