ASO keyword research still asks for a search count Apple does not sell. AppsOps and AppDrift writeups in 2026 repeat the same limit: Apple Search Ads exposes a popularity index from 5 to 100 to advertisers, and vendors model the rest. Trends API does not fill that hole with a fake App Store volume. It scores an Android bundle ID. POST https://api.trendsapi.ai/api. Bundle-ID rules sit on the App Store guide. Endpoint fields sit on the API reference. The series is inside the string body, not beside it.
Three different 0-100 scales
Apple Search Ads popularity is Apple's relative index inside an ads account. ASO vendors build a second 0-100 from that index plus autocomplete and ranks. source app rankings is a third series: this product's score for a bundle ID. Do not join them as one column. Do not put a metadata keyword such as photo editor into app rankings. The keyword must be com.something.app.
Downloads are the longer ASO tape
POST https://api.trendsapi.ai/api
Authorization: Bearer <api_key>
Content-Type: application/json
{"mode":"get_growth","source":"app downloads, app rankings","keyword":"com.openai.chatgpt","percent_growth":["3M","12M"]}
The same bundle ID on app downloads (checked 27 Aug 2026) is an install tape. It is not a popularity score for a title token. Use it to see whether installs are still arriving after a metadata change. Pick the words themselves from ASA and App Analytics.
app rankings for the same ID could not complete 3M or 12M (date_out_of_range). A follow-up on 7D, 14D, and 30D returned no_data. An ASO dashboard that requires a 12M rank slope will be empty. Ship a 30-day rank job only after a short window succeeds.
Charts still do not take a keyword
get_top_trends type Google Play on 27 Aug 2026 listed WhatsApp Messenger first. That row is not an ASO keyword. It is a chart title. Metadata research stays in the ads account and in first-party search terms. This API answers whether the Android app's installs are rising after the metadata change, on a delay.