Hashtags, sounds, and trending topics as data

Hashtags, sounds, and trending topics are named clusters, not user accounts. Instagram and TikTok hashtags, TikTok music ids and Instagram audio ids, X trends, YouTube trending. They answer “what is moving,” not “who is this person.”

Google Trends the product stays out — different entity. We do not host audio files; the sound is a JSON object (ids, posts that used it). Google News topics are cousins on another host: headlines, not hashtags.

Creator lookup is the person. This note is the cluster. Mixing them is how a newsroom treats a hashtag as a user and then wonders why resolve failed.

Topic objects across hosts

IG: hashtag posts and hashtag reels. TikTok: hashtag handle, hashtag posts, music posts. YouTube: hashtag tag, trending. X: trends.

curl -H 'Authorization: Bearer bby_live_…' 'https://tiktok.fetcher.sh/api/hashtag/handle/ai'

Access notes for Instagram, TikTok, YouTube, and X still apply.

A sound id is not an mp3 we host. A trend on X is not a Google Trends search-interest graph. A News topic id is not a TikTok hashtag. If the question is “who is this account,” do not start here.

Google Trends is a different product

Google Trends is a search-interest graph over Google queries. X trends are what X is showing as trending. YouTube trending is a catalog list. Hashtags are named clusters of posts. Those four sentences are why a single “trends API” search retrieves chaos.

Use Google Trends if that is the product you mean. Use this catalog if you mean social topic objects as JSON. Use News topics if you mean headline topics. Pay for the GET that matches the sentence.

A case: a hashtag that jumped overnight

A newsroom sees #ai on TikTok in the morning meeting. They need public posts under that hashtag, not a Google Trends screenshot, and they need the sound ids that keep repeating.

They fetch the hashtag handle, list posts, and read music entities off the top rows. They do not download audio. They do not treat the hashtag as a user. If they then want the creator behind a post, they switch to profile lookup.

News topics as headlines stay on google-news.fetcher.sh. Social topic objects stay here.

A case: a sound, not a hashtag

The TV moment attached to a sound, not a tag. They start from a post, read the music id, list music posts, sort by recency. Hashtag search would have missed half the cluster because people did not tag.

That is why sounds are first-class on TikTok (and audio on IG) instead of a footnote under hashtags. The object in the JSON is the cluster key.

X trends are a snapshot of what X is showing, not a history of every trend that ever existed. If you need a time series, you store the snapshot yourself on a schedule. YouTube trending is a catalog list, similarly not Google Trends. Hashtag posts page; they are not “every post that ever used this tag in the history of the app.”

News topic ids stay on google-news.fetcher.sh. If a morning meeting says “topics,” ask which product they mean before you fetch.

A desk that wants this as a feed stores yesterday’s hashtag post ids and diffs today’s. That is “what is moving,” not Google Trends. Sounds get the same treatment: music id in, new posts out, no mp3. X trends get a timestamped snapshot in object storage because the product will not remember Tuesday for you.

If the cluster is actually a person, you have finished this note. Resolve the handle. List recent posts. Stop tagging them as a hashtag in your own spreadsheet — that confusion is how a creator brief cites a sound id as a user id.

Clusters, not people, not Google Trends

Google Trends is a search-interest graph. X trends, YouTube trending, and hashtag/sound objects are not that graph. A sound id is not an mp3 we host. If the question is “who is this account,” do not start here. Docs on the hosts; 402 or a key. Creator lookup is next door when the cluster has a face. Trending lists go stale in hours; if you need history, you snapshotted it. We will not replay Tuesday’s X trends on Friday. That limitation is honest. A Trends screenshot in a slide deck is a different product with a different name. Hashtag handles are not user handles. Music ids are not hashtags. X trends are not News topics. Put the object type in the column header or you will brief a sound as if it were a person. We still do not host the audio; the JSON is the cluster, not the file. Snapshot trends if you need yesterday; the host will not remember it.