get_top_trends ranks a live board. Leave sort off, or set it to rank, for current leaders. Set sort to rank_change when the question is who climbed. window then picks the lookback. The rest of the POST is unchanged: type, optional category, limit, offset. How to form the board call is on get_top_trends. Allowed lookbacks sit on rank_change windows.
Current rank versus climbers
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. as_of_ts is still the current snapshot time. data order is now climb, not current rank 1.
A newsroom spike list is rank_change. A "top 10 now" widget is rank. Do not send sort on get_growth. That mode has no board.
The extra fields
Default rows are [rank, label] arrays. A rank_change row is an object with rank, keyword, prev_rank, and rank_change. rank_change is the climb or drop versus the prior snapshot. It is not a 0-100 score and not a percent_growth value.
limit and offset still page the list. That is feed pagination, not a different sort.
window is not a growth preset
7d is a live-feed lookback. 7D is a get_growth preset. Mixing the two fails the field that received the wrong token. window without sort rank_change does nothing useful.
Short windows (1d, 3d, 7d) only work on daily feeds. If the inner payload is a note instead of rows, lengthen window. Caps stay on pricing.