A live feed is a ranked board, not a keyword series. Set mode to get_top_trends. Set type to an exact feed label. Do not send keyword or source. The HTTP call is still POST https://api.trendsapi.ai/api with a Bearer key. The envelope is {"statusCode": int, "body": string}. Parse body before reading data. Field tables for modes sit on the API reference. The type strings sit on the feed type catalog.
The request has no keyword
get_time_series and get_growth answer "how is this term moving." get_top_trends answers "what is on this board right now." Mixing the two field sets is a 400.
POST https://api.trendsapi.ai/api
Authorization: Bearer <api_key>
Content-Type: application/json
{"mode":"get_top_trends","type":"Google Trends","limit":10}
App Store Top Free, App Store Top Paid, and Google Play are live store charts. They are not a substitute for source app downloads or app rankings on a keyword call. That distinction is on the Android bundle ID page.
Fields the mode accepts
| Field | Required | Notes |
|---|---|---|
mode |
yes | get_top_trends |
type |
yes on MCP | Exact label. Omit on REST to return every feed |
category |
on four types | See category feeds |
limit |
no | Default 25, max 200, min 1 |
offset |
no | Default 0 |
sort |
no | rank (default) or rank_change |
window |
only with rank_change |
1d, 3d, 7d, 14d, or 30d. Default 30d |
window without sort rank_change does nothing useful. Lookback rules sit on rank_change windows.
Parse the envelope, then the board
The inner object, after the second parse, has as_of_ts, type, limit, offset, count, and data. Default data rows are [rank, label]. A rank_change row adds prev_rank and rank_change.
Labeled sample shape, not a live pull:
{
"as_of_ts": "2026-03-26T22:22:25Z",
"type": "Google Trends",
"limit": 10,
"count": 10,
"data": [[1, "example term"]]
}
as_of_ts is the snapshot time. Cache against that, not against the HTTP date.
When to use a different mode
Need weekly history for one term? get_time_series plus a source. Need percent change over 3M or 12M? get_growth. Those modes are documented on the API reference. Plan names stay on pricing. Per-platform guides start at https://trendsapi.ai/trends.