Twitter / X Trends API
Pull Twitter/X trending topics by location before you decide what to search, monitor, or summarize
Trending topics are useful when they become the starting point for a workflow: a dashboard, content brief, market scan, campaign monitor, or AI summary. TwtAPI gives developers a practical Trends API path for retrieving location-specific Twitter/X trends by WOEID, then connecting those topics to search, monitoring, reports, and downstream automation.
Quick Take
Start with the decision, then read deeper if you need to
If you only need the fast decision frame, start with these points before reading the rest of the page.
Where trends fit
Trends are rarely the final answer. They are usually the discovery layer before deeper search and review.
- Retrieve current Twitter/X trends for global, country, region, or city-level analysis when a WOEID is available.
- Worldwide trends, country trends, and city trends can tell very different stories. WOEID selection should match the market you actually care about.
- Get trending topics for supported locations, including names, search URLs, and tweet volume when available.
- Use location-specific trends to spot topics worth investigating before turning them into briefs, posts, or review queues.
Decision Guide
The practical decision this page should help you make
Use this route when
Use location-specific trends to spot topics worth investigating before turning them into briefs, posts, or review queues.
Choose another route when
Do not use this as the only answer if the job needs a full social suite, official account write actions, ads, DMs, or a budget decision that has not been modeled yet.
First test to run
Start with global, country, region, or city WOEIDs that match the markets your team actually watches.
Success signal
Worldwide trends, country trends, and city trends can tell very different stories. WOEID selection should match the market you actually care about.
Who It Fits
Best for teams that need trend signals inside a repeatable workflow
A trends endpoint is most useful when it feeds a decision or downstream job instead of becoming a standalone curiosity dashboard.
Content and editorial teams
Use location-specific trends to spot topics worth investigating before turning them into briefs, posts, or review queues.
Market and audience research teams
Track what is moving across regions and compare trend signals with search results, accounts, and audience language.
Developers building dashboards or agents
Poll trends on a schedule and let your own workflow route relevant topics to dashboards, Slack digests, AI summaries, or monitoring workflows.
Regional GTM and comms teams
Use trends when the same brand, event, or category behaves differently across countries, cities, or launch markets and the team needs local context before acting.
Why This Matters
Trend polling is simple to prototype and easy to misuse at scale
SERP and developer discussions show the same pattern: people want trending topics by location, but the real decision is how often to poll, which regions matter, and what happens after a topic appears.
Location matters
Worldwide trends, country trends, and city trends can tell very different stories. WOEID selection should match the market you actually care about.
Polling cadence changes cost
A dashboard that refreshes a few regions hourly is a different workload from polling many locations every few minutes.
Trends need a second step
A trend name alone is rarely enough. Teams usually need to search posts, inspect accounts, and decide whether the topic is noise, opportunity, or risk.
Trend names can be ambiguous
A short phrase may refer to a person, show, token, sports event, political topic, or meme. Search a sample of posts before routing a trend into a report or AI summary.
A useful trend workflow filters aggressively
Do not alert on every trend. Filter by region, language, business topic, blocked terms, volume movement, and whether the topic has enough example posts to justify review.
Trends should trigger questions, not conclusions
A trend name tells you that something is moving, not why it matters. Treat it as a prompt to collect examples, inspect sources, and decide whether the topic is relevant to your market, campaign, or risk model.
Regional comparison needs the same cadence
If you compare cities or countries, poll them on the same schedule and keep the same filters. Otherwise a difference in timing can look like a difference in market behavior.
Relevant TwtAPI Capabilities
Use trends as the discovery layer, then decide what deserves deeper retrieval
Trend data works best when it is connected to search and monitoring instead of sitting alone.
| Area | What to check | Why it matters |
|---|---|---|
| Trends | Retrieve trends by WOEID | Get trending topics for supported locations, including names, search URLs, and tweet volume when available. |
| search_tweets | Search posts around a trend | Use tweet search when a trend needs context, examples, sentiment, or source review. |
| get_user_by_username | Add account context | Enrich the accounts shaping a trend before routing them into a report or AI summary. |
| monitoring | Turn repeated trend checks into a workflow | Route selected trends into Slack, Sheets, dashboards, webhook handlers, or AI-assisted summaries. |
Workflow Pattern
A practical trends workflow moves from location to trend to context
The useful version is not just polling the trend list. It is deciding what each trend should trigger.
- 1
Choose the locations that matter
Start with global, country, region, or city WOEIDs that match the markets your team actually watches.
- 2
Poll at a cadence you can afford
Set a refresh schedule that matches the decision cycle: hourly digest, daily brief, live dashboard, or incident watch.
- 3
Promote only meaningful trends into search
Filter by topic, keyword, region, or tweet volume before spending more calls on deeper retrieval.
- 4
Send the result into the tool that owns the decision
Push selected trends into Sheets, Slack, Notion, a dashboard, a queue, or an AI summary workflow.
- 5
Attach example posts before summarizing
Before asking an analyst or model to explain a trend, collect representative posts and source URLs. Trend names without examples often produce shallow or misleading summaries.
- 6
Review the trend list against a denylist
Maintain blocked topics, recurring spam, irrelevant entertainment terms, and known false positives so the workflow does not waste attention on trends the team will never act on.
- 7
Store the trend snapshot before enrichment
Save the WOEID, trend name, query URL, tweet volume when available, polling time, and region before searching posts. That snapshot lets you explain why a trend entered the workflow later.
- 8
Promote only reviewed trends into reports
Before a trend reaches a content brief, market note, or executive summary, attach example posts, source accounts, region, time observed, and a short human note about why the topic matters.
- 9
Stop enrichment when the trend has no decision owner
A trend can be real and still irrelevant. If nobody owns the market, campaign, incident, content, or risk decision, keep the snapshot but do not spend extra calls explaining it.
- 10
Label every promoted trend with a next action
A trend should become search, watch, brief, alert, or ignore before it leaves the trends workflow. That label keeps dashboards, content teams, and AI summaries from treating every moving topic as equally important.
- 11
Compare trend movement against the normal local pattern
Some locations trend entertainment, sports, politics, or recurring spam every day. Keep a baseline so the team can tell a meaningful topic from normal local noise.
FAQ
Questions teams ask before using a Twitter Trends API
These answers focus on implementation decisions developers and research teams usually need to make.
What is a Twitter Trends API used for?
It is used to retrieve current Twitter/X trending topics for specific locations, then feed those topics into dashboards, content planning, market research, monitoring, alerts, or AI summaries.
What is WOEID in a trends API?
WOEID means Where On Earth ID. It identifies a geographic location such as worldwide, a country, a region, or a city. Trends by WOEID return topics for that location when supported.
Is trends data enough for market research?
Usually not by itself. Trends help discover what is moving, but teams often need tweet search, account context, timelines, and human or AI review to understand why it matters.
How should I evaluate a trends API?
Compare supported locations, response shape, tweet volume availability, pricing, rate limits, polling cadence, retries, and how easily trend names can feed search, monitoring, and reports.
How often should I poll trends?
Match cadence to the decision. A daily content brief can poll slowly. A live event dashboard may need a tighter cadence. Polling many locations every few minutes should be modeled against cost and review capacity first.
What should happen after a trend appears?
Search posts around the trend, collect examples, check the accounts shaping it, filter irrelevant topics, and route only the trends that match the team’s market, campaign, or risk criteria.
What should I store from a trends API response?
Store the WOEID, location name, trend name, query URL, tweet volume if present, polling timestamp, matched filters, and whether the trend was promoted into search or ignored.
How do I keep trend alerts from becoming noise?
Use a region list, allowlist business topics, denylist recurring junk, minimum movement rules, and a review step before pushing trends into Slack, dashboards, or AI summaries.
What should happen after a trend is promoted?
Give it a next-action label: search for examples, watch for movement, brief a team, alert an owner, or ignore after snapshotting. Without that label, trend polling becomes a novelty feed instead of a workflow.
Next step
Use trends as a starting point, then decide what deserves deeper work
Start with one region, one polling cadence, and one downstream destination. Then connect trend signals to search, monitoring, or AI summaries.