Trends24 APItrends24.in ↗
Fetch the current worldwide X/Twitter trending topics via the Trends24.in API. Get 50 ranked trends with tweet counts and search URLs, updated hourly.
What is the Trends24 API?
The Trends24.in API exposes a single endpoint, get_worldwide_trends, that returns a ranked list of 50 worldwide X/Twitter trending topics in one call. Each trend object includes its rank, topic name, tweet count (when available), and a direct X search URL. The snapshot is refreshed roughly every hour, making it suitable for dashboards, alerting systems, or any application that needs a current read on global Twitter activity.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/f0661f54-a855-4424-b8b5-edacb61975ea/get_worldwide_trends' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace trends24-in-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: Trends24 SDK — fetch current worldwide Twitter/X trends."""
from parse_apis.trends24_in_api import Trends24, ParseError
client = Trends24()
# Get the full snapshot including metadata and all trends
try:
snapshot = client.snapshots.get()
except ParseError as e:
# Raised when the upstream source changes shape or is unreachable
print(f"Source extraction failed: {e}")
raise
print(f"Snapshot updated: {snapshot.updated_at}")
# Iterate the top 10 trending topics via the paginated list
for trend in client.trends.list(limit=10):
print(f"#{trend.rank} {trend.topic_name} — {trend.url}")
print("exercised: snapshots.get / trends.list")
Returns the current worldwide X/Twitter trending topics list. Each call fetches the most recent snapshot (updated roughly hourly) of 50 trending topics with their rank, topic name, tweet count (when available from the source), and the X/Twitter search URL for that topic. Tweet counts may be null when the source does not provide volume data for the worldwide view.
No input parameters required.
{
"type": "object",
"fields": {
"trends": "Array of 50 trending topic objects, ordered by rank",
"timestamp": "Unix timestamp (seconds) of the snapshot",
"updated_at": "UTC timestamp string indicating when this trend snapshot was captured"
},
"sample": {
"data": {
"trends": [
{
"url": "https://twitter.com/search?q=%23Popstars",
"rank": 1,
"topic_name": "#Popstars",
"tweet_count": null
},
{
"url": "https://twitter.com/search?q=%23WWERaw",
"rank": 2,
"topic_name": "#WWERaw",
"tweet_count": null
},
{
"url": "https://twitter.com/search?q=Chelsea",
"rank": 3,
"topic_name": "Chelsea",
"tweet_count": null
}
],
"timestamp": 1787625967.853,
"updated_at": "Tue Aug 25 2026 02:46:07 GMT+0000 (Coordinated Universal Time)"
},
"status": "success"
}
}About the Trends24 API
What the API Returns
The get_worldwide_trends endpoint takes no input parameters and returns a single structured snapshot of global X/Twitter trends. The top-level response includes a trends array of 50 objects ordered by rank, a timestamp field in Unix seconds, and an updated_at UTC string showing when the snapshot was captured. Each trend object in the array carries the trend's numeric rank, its display name (a hashtag, keyword phrase, or named topic), the tweet count string where the source provides one, and a pre-built X search URL you can use to link directly to live tweets for that topic.
Response Field Details
The tweet_count field is not always populated — Trends24.in only surfaces a count when the underlying data includes one, so your integration should treat it as optional. The timestamp and updated_at fields refer to the same moment but in different formats, useful depending on whether your pipeline handles epoch integers or ISO-style strings. The trends array is always 50 items, ordered ascending by rank (rank 1 is the top trend).
Freshness and Coverage
The snapshot reflects worldwide aggregated trend data, not country- or city-level breakdowns. Updates happen approximately hourly, so two calls within the same hour may return identical data. If you need to detect when the list changes, compare the timestamp field across calls — a new value indicates a fresh snapshot has been captured.
The Trends24 API is a managed, monitored endpoint for trends24.in — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when trends24.in changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official trends24.in API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Display a live worldwide trending topics widget on a news or social dashboard using the ranked
trendsarray - Trigger content alerts when specific keywords appear in the top 10 ranks by polling
get_worldwide_trendshourly - Build a trend history database by storing each
timestamp-keyed snapshot to analyze how topics rise and fall over time - Generate pre-built X search links for a media monitoring tool using the
urlfield in each trend object - Identify emerging hashtags without a
tweet_countvalue to flag early-stage trends before volume data is reported - Feed trend data into a content calendar tool that suggests topics based on current worldwide conversation peaks
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Trends24.in have an official developer API?+
Does the API cover country- or city-level trends, not just worldwide?+
get_worldwide_trends endpoint returns only the global worldwide snapshot. You can fork this API on Parse and revise it to add a country- or city-level trends endpoint.Is the tweet count always present in the trend objects?+
tweet_count field is populated only when the source includes a volume figure for that trend. Trends without a reported count will have a null or empty value for that field, so your code should handle both cases.How do I know if the data has been refreshed since my last call?+
timestamp Unix field across calls. If the value is the same as your previous response, the snapshot has not changed. A new timestamp value indicates the trend list has been updated, typically on an approximately hourly cycle.Does the API return historical trend data or only the current snapshot?+
get_worldwide_trends reflects the most recent captured state; no historical or time-series endpoint is included. You can fork this API on Parse and revise it to persist and serve historical snapshots if your use case requires trend history.