X's developer platform is a paid product with its own tiers and rules. Scraping old Twitter WOEID trend URLs is a third path and a brittle one. Trends API exposes the live board as get_top_trends with type X (Twitter) Trending. The caller never holds an X token. body is a JSON string and must be parsed a second time. Docs: the API reference. X notes: the X guide. Caps: pricing.
Paid X developer tiers
X documents application access and paid tiers on its developer site. Those credentials are correct for posting, user lookup, or a firehose. They are the wrong dependency when the job is a ranked trending list next to Google and Reddit in one JSON envelope. Do not paste an X token into the Trends API header.
type X (Twitter) Trending
POST https://api.trendsapi.ai/api
Authorization: Bearer <api_key>
Content-Type: application/json
{"mode":"get_top_trends","type":"X (Twitter) Trending","limit":25}
The type string is exact. limit defaults to 25. offset pages. This is a labeled request shape, not a frozen list of names. Names on that board move through the day.
Location WOEID scrapes are not this feed
Unofficial Twitter snippets used a WOEID to pick a city board. That parameter does not exist here. There is no pn, no geo, and no WOEID field on this POST. If a city slice is mandatory, that is still an X-platform problem, not a missing Trends API flag.
Search volume is a different source
There is no keyword source named x or twitter on get_growth. The live board is the X product in this API. Web search interest in a cashtag or a handle is source google search on a second call. Keep the join in the caller.