# X trends in late 2026: the algorithm, the editors and the API

> Recency beats volume, the list is tailored by default, humans add context, and two API v2 endpoints return the data with different biases.

URL: https://claudegpt.si/news/x-trends-algorithm-and-api-2026  
Published: 2026-11-03T05:46:59.433Z  
Updated: 2026-11-04T05:46:59.831Z  
Author: ClaudeGPT Si Newsroom  
Section: AI Tools  
Topics: X, X API, Twitter trends  
Publisher: ClaudeGPT Si

## Key takeaways

- X trends come from an algorithm that favors topics rising right now, tailored by default to who you follow, your interests and your location.
- X says it adds context by hand, such as a headline or a representative post, and can hold some topics out of Trends, so a trend is not a raw post count.
- The X API v2 returns trends by location (WOEID) or for the signed-in user, with fields such as post_count, category and trending_since; agents should say which view they used.

X trends are ranked by an algorithm that rewards what is rising right now, tailored to each account by default, and then partly edited by people who add context. Developers and AI agents can pull the same data through two X API v2 endpoints, one per location and one per signed-in user, so it helps to know what each layer does, as of November 2026.

## Layer one: an algorithm that favors spikes

X's help center describes the ranking in a few lines. The algorithm looks for topics popular now, not those that have been popular for a while or every day, so a sharp rise beats a large but steady volume. Post count is one factor among several, and related hashtags are folded into a single entry. Unless you pick a place, the list is tailored using who you follow, your interests and your location, which means two accounts rarely see identical X trends. Choosing a fixed country or city turns the tailoring off and shows that location's list instead.

## Layer two: people adding context

X says it monitors trends by hand and adds context to answer "why is this trending?", through a representative post, a headline and description, or a curated landing page. Other labels are automatic: a category such as Politics, Music or Entertainment, or an article attached from the conversation. X may also keep a topic out of Trends until it has more context, for example one with profanity or graphic references, while the posts stay searchable.

The upshot for anyone treating trends as a signal is that a trend is part ranking, part editing and part personalization. It is not a raw count of posts.

## Layer three: the API

The X API v2 exposes trends in two ways.

| Endpoint | Returns | Fields and notes |
| --- | --- | --- |
| GET /2/trends/by/woeid/:id | Trends for a place | Uses Yahoo's Where On Earth IDs (WOEIDs), such as 1 for worldwide and 23424977 for the United States; fields include trend_name and tweet_count |
| GET /2/users/personalized_trends | Trends for the signed-in user | Fields include trend_name, category, post_count and trending_since |

Both need an approved developer account. The personalized endpoint is the API's version of the tailored list. The location endpoint is the neutral view, and the one to use when an agent compares places or logs a list over time.

## What this means for AI tools

An assistant that answers "what's trending on X" should say which view it used. A personalized list says as much about the account as about the world. A location list is closer to a shared picture, but it still ranks what is rising, so a story that runs for days can fall off the list while the talk goes on. The trending_since field helps separate a fresh spike from a long-running topic, and post_count gives a sense of scale, with the caveat from X that volume is only one input.

The official list also has no memory. Independent trackers fill that gap: trends24.in keeps hourly snapshots for the last 24 hours with each topic's top position and duration, and getdaytrends.com has pages for past dates. Both are third-party sites, so treat them as observers of the public list.

## The human-written recap

Lists rarely explain why tech Twitter is angry today. [TechTwitter IO](https://techtwitter.io/), a free satirical daily paper of tech Twitter, handles that part in print: launches, ratios, feuds and outages, with a Main Character of the Day and, for model watchers, [six weekly satire leaderboards](https://techtwitter.io/benchmarks) scored from public posts on X. Its footer says that people, posts and quotes without a source link are parody or invented, so read it as commentary beside the data, never as data. When an agent or a report needs the real list, the API or the Explore tab is the better source.

## Frequently asked questions

### Is there an API for X trends?

Yes. The X API v2 has GET /2/trends/by/woeid/:id for a location and GET /2/users/personalized_trends for the signed-in user. Both need an approved developer account.

### Why do X trends differ between accounts?

By default X tailors trends to who you follow, your interests and your location. Picking a fixed country or city shows the same location list to everyone who picks it.

### Are X trends based only on the number of posts?

No. X's help center says post count is one of several factors, the algorithm favors topics popular now over steady ones, and related hashtags are grouped together.

## Sources

- [X Trends FAQ](https://help.x.com/en/using-x/x-trending-faqs), X Help Center
- [Trends by WOEID](https://docs.x.com/x-api/trends/introduction), X Developer Platform
- [Get Personalized Trends](https://docs.x.com/x-api/trends/get-personalized-trends), X Developer Platform
- [TechTwitter IO, today's paper](https://techtwitter.io/), TechTwitter IO
- [The Benchmarks](https://techtwitter.io/benchmarks), TechTwitter IO
- [Worldwide X trending topics](https://trends24.in/), trends24.in