app downloads and app rankings are keyword sources. The keyword is an Android bundle ID. They are not the App Store and not Google Play's live boards. Those boards are get_top_trends feeds: App Store Top Free, App Store Top Paid, and Google Play. No keyword on a board. Mixing a display name into app downloads fails. Mixing a bundle ID into type Google Play is the wrong mode. body is a JSON string and must be parsed a second time. Mode list: the API reference. Store-facing notes: the App Store guide. Plan text: pricing.
Keyword history needs an Android bundle ID
The string is the id= value on play.google.com/store/apps/details?id=. com.openai.chatgpt is valid. ChatGPT is not. If app downloads is combined with other sources on get_growth, the keyword is still the bundle ID for the whole call.
POST https://api.trendsapi.ai/api
Authorization: Bearer <api_key>
Content-Type: application/json
{"mode":"get_growth","source":"app downloads","keyword":"com.openai.chatgpt","percent_growth":["12M"]}
A live pull on 2026-08-27 for com.openai.chatgpt on app downloads returned 12M growth of +63.93 percent (10.0 vs 6.1) with recent_volume 7293948. The same day's pull for com.whatsapp on app downloads and on app rankings returned no_data.
Live boards are store charts
{"mode":"get_top_trends","type":"Google Play","limit":5}
A live Google Play board on 2026-08-27 returned WhatsApp Messenger, Facebook, YouTube, Instagram, and Free Fire: 9th Anniversary as the first five names. Those strings are chart labels. They are not bundle IDs and they are not valid app downloads keywords.
A 404 no_data on a bundle ID
no_data means the store of series has no points for that pair. It is not a typo report. Log the keyword and source. Do not retry with the human name. Do not retry with an iOS id. Try app rankings as a second source only when a rank series is the question. It can also return no_data.
Same key, two modes, do not mix the keyword
History: get_growth or get_time_series, source app downloads or app rankings, keyword com.something. Chart: get_top_trends, type Google Play or an App Store feed, no keyword. The product MCP server at https://api.trendsapi.ai/mcp uses the same split. A pipeline that stores both should keep two tables.