get_top_trends defaults to current rank. Set sort to rank_change to rank by climb against a prior snapshot. window then selects the lookback. Valid strings, from the Trends API MCP server in this session: 1d, 3d, 7d, 14d, 30d. Default window is 30d. The rest of the call is unchanged: type, optional category, limit, offset. How to form the POST is on the live feeds page. Labels sit on the feed catalog.
rank versus rank_change
sort |
Board order | Extra fields |
|---|---|---|
rank (default) |
Current leaders | [rank, label] |
rank_change |
Biggest climbers vs the snapshot | prev_rank, rank_change |
POST https://api.trendsapi.ai/api
Authorization: Bearer <api_key>
Content-Type: application/json
{"mode":"get_top_trends","type":"Google Trends","sort":"rank_change","window":"7d","limit":10}
Parse the string body before reading data. as_of_ts is still the snapshot time for the current board.
Allowed lookbacks
window |
Use |
|---|---|
1d |
Daily feeds only |
3d |
Daily feeds only |
7d |
Daily feeds only |
14d |
Longer lookback |
30d |
Default |
The MCP server states that short windows only work on daily feeds. Weekly and monthly feeds return a note pointing to a longer window. If a pull comes back with that note, raise window rather than retrying the same string.
1d is not 1D. These tokens are lowercase with a d. They are not the 7D / 1W presets used on get_growth. Those presets live on growth windows.
Fields on a mover row
A rank_change row includes current rank, the label, prev_rank, and rank_change. rank_change is the climb (or drop) vs the prior snapshot, not a 0-100 score. Category-gated types still need category. Official names sit on category feeds.
When to keep default rank
Use rank when the question is "who is on top right now." Use rank_change when the question is "who moved." A newsroom spike hunt and an ASO chart-climber list are rank_change jobs. A "top 10 now" widget is rank.
The HTTP contract is on the API reference. Plan names stay on pricing.