X/Twitter Trends Scrapper avatar

X/Twitter Trends Scrapper

Pricing

from $0.30 / 1,000 results

Go to Apify Store
X/Twitter Trends Scrapper

X/Twitter Trends Scrapper

Stay on top of what is trending on X and react faster to topics that are gaining momentum now.

Pricing

from $0.30 / 1,000 results

Rating

0.0

(0)

Developer

simoit

simoit

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Share

Trends Scraper

SIMO IT logo

Stay on top of what is trending on X and collect both trend timelines and relevant accounts from the topics gaining momentum now.

About SIMO IT

SIMO IT builds practical social data products that support fast insight loops for marketing, PR, and growth teams.

Features

  • collect posts from selected trend timelines
  • follow categories like trending, news, sport, and entertainment
  • collect TrendRelevantUsers for a selected trend (people driving the topic)
  • monitor topic momentum and context
  • paginate for deeper trend analysis

Use cases

  • trendwatching and social listening
  • real-time content planning
  • spotting opportunities for rapid PR and marketing reactions

Output

Fresh trend-related content that can be used immediately in analysis, planning, and decision workflows.

Note: backend endpoint returns an envelope: { data: [...], page, limit, has_next }. This Actor pushes only records from data[] to the dataset.

How to use

  1. Open the Actor on Apify.
  2. Provide trendId/category or trendUrl (batch supported via CSV/new-line URL inputs).
  3. Choose dataMode: trends, relevant_users, or both.
  4. Configure pagination for broader coverage.
  5. Run the Actor and use the dataset output.

No technical setup is required from your side. Backend infrastructure is managed by SIMO IT.

Input

  • trendId (string, conditionally required): Trend timeline/category ID (for example trending, news, sport, entertainment).
  • category (string, optional): Preset alias for trend timelines.
  • trendUrl (string, optional): Single X/Twitter trend URL.
  • trendUrls (string, optional): Batch trend URLs (comma-separated or new lines).
  • startUrls (string, optional): Alias batch URL input (comma-separated or new lines).
  • dataMode (string, optional, default: trends): trends, relevant_users, or both.
  • page (integer, optional, default: 1): Starting page number.
  • limit (integer, optional, default: 20, max: 100): Records per page.
  • maxPages (integer, optional, default: 1): Maximum number of pages to fetch.
  • maxItems (integer, optional): Hard cap for trend records.
  • usersPage (integer, optional, default: 1): Starting page for trend relevant users.
  • usersLimit (integer, optional, default: 20, max: 100): Relevant users per page.
  • usersMaxPages (integer, optional, default: 1): Maximum pages for trend relevant users.
  • usersMaxItems (integer, optional): Hard cap for trend relevant user records.

Filters and pagination

  • trend target: trendId, category, trendUrl, trendUrls, startUrls
  • mode switch: dataMode
  • trend page controls: page, limit, maxPages, maxItems
  • relevant users page controls: usersPage, usersLimit, usersMaxPages, usersMaxItems

Example input

{
"category": "trending",
"dataMode": "both",
"trendUrls": "https://x.com/trending",
"limit": 20,
"maxItems": 50,
"usersMaxItems": 50
}

Example output

{
"id": "trend-AI agents",
"rank": null,
"name": "Vikings Receiver Rondale Moore Dies at 25 in Apparent Suicide",
"trend_url": {
"url": "twitter://trending/2025383938727051697",
"urlType": "DeepLink",
"urlEndpointOptions": []
},
"trend_metadata": {
"domain_context": null,
"url": {
"url": "twitter://trending/2025383938727051697",
"urlType": "DeepLink",
"urlEndpointOptions": []
},
"meta_description": null,
"name": "Vikings Receiver Rondale Moore Dies at 25 in Apparent Suicide"
},
"grouped_trends": [],
"_type": "timelinetrend"
}
{
"id": 44196397,
"username": "elonmusk",
"name": "Elon Musk",
"followersCount": 235240499,
"friendsCount": 1288,
"verified": true,
"_type": "snscrape.modules.twitter.User"
}

FAQ

Do I need my own backend or API setup?
No. This Actor is ready to run on Apify, and backend infrastructure is managed by SIMO IT.

Which values can I use for trendId?
Common options include trending, news, sport, and entertainment.

Can I collect trend data continuously?
Yes. Run the Actor on a schedule and paginate with maxPages.

How do I get users for a specific trend topic?
Set dataMode to relevant_users or both, and optionally tune usersLimit / usersMaxPages.