mcpField
A
App Store Trends API

App Store Trends API

Remote
trendsapi.aiData & Analytics0Updated 10w ago

About App Store Trends API

App Store Trends API provides Android app-download history and live iOS and Google Play charts through Python, JavaScript, or HTTP. It is for analyzing app demand, with historical keyword data and live chart feeds offered separately.

Key features

  1. 01Retrieve app-download time series
  2. 02Measure growth across date ranges
  3. 03Read live App Store charts
  4. 04Read live Google Play charts
  5. 05Use async Python client
  6. 06Access through HTTP API

Use cases

  1. 01Track Android downloads by bundle ID
  2. 02Compare app-download growth across periods
  3. 03Review current iOS rankings
  4. 04Check Google Play chart positions

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://app-store.api.trendsapi.ai/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://app-store.api.trendsapi.ai/mcpAuth required

Tools

Details

From the project README

App Store and Google Play chart API

App Store and Google Play demand via the Trends API. Android download history plus live iOS and Play charts.

License: MIT PyPI Python

Key: trendsapi.ai/#get-key. HTTP contract and every source: trendsapi-ai/trendsapi.

Authentication

pip install trendsapi-app-store
export TRENDSAPI_KEY=your_key

Python 3.9+. Same key as the HTTP API.

from trendsapi_app_store import TrendsAPI

client = TrendsAPI()                    # TRENDSAPI_KEY
# client = TrendsAPI(api_key="YOUR_KEY")

Keyword helpers default to source: "app downloads". Pass source= to hit any other platform with the same client. Official full client (every source, no preset): trendsapi.

Methods

MethodREST modeReturns
get_time_series(keyword, source=, data_mode=)get_time_serieslist[TrendsDataPoint]
get_growth(keyword, percent_growth=, source=, data_mode=)get_growthGetGrowthResponse
get_live(limit=, offset=, category=)get_top_trendsGetTopTrendsResponse
get_top_trends(type=, ...)get_top_trendsGetTopTrendsResponse

source is lowercase (app downloads). type is exact (App Store Top Free). Mixing them is a 400.

from trendsapi_app_store import TrendsAPI

client = TrendsAPI()                    # TRENDSAPI_KEY
# client = TrendsAPI(api_key="YOUR_KEY")

series = client.get_time_series("com.openai.chatgpt")
print(series[-1].date, series[-1].value)

growth = client.get_growth("com.openai.chatgpt", percent_growth=["3M", "12M"])
print(growth.results[0].growth, growth.results[0].direction)

hot = client.get_live(limit=10)
print(hot.data)                         # [[1, "..."], ...]

get_time_series

points = client.get_time_series("com.openai.chatgpt")

Each point:

FieldAlwaysMeaning
dateyesYYYY-MM-DD
valueyes0-100 index for this series
keywordyesEcho
volumenoAbsolute volume when available
source or datatypenoPipeline label

Python returns list[TrendsDataPoint]. Use .date and .value, not ["date"]. JS returns the same fields as object properties.

get_growth

g = client.get_growth("com.openai.chatgpt", percent_growth=["12M", "3M", "YTD"])
print(g.results[0].growth, g.results[0].direction)

percent_growth default: ["12M"]. Presets: 7D 14D 30D 1M 2M 3M 6M 9M 12M/1Y 18M 24M/2Y 36M/3Y 48M 60M/5Y MTD QTD YTD. Custom: {"name": "Launch", "recent": "2024-06-01", "baseline": "2024-01-01"}.

FieldMeaning
search_termKeyword
data_sourceSource
resultsOne object per window (period, growth, direction, dates, values)
metadataCounts / success flag

Several windows still count as one request. Python: growth.results[0].growth. JS: growth.results[0].growth.

get_live

hot = client.get_live(limit=10)
FieldMeaning
as_of_tsSnapshot time
typeFeed name
limit, offset, countPagination
data[rank, label] rows

Python: hot.data. JS: hot.data. Optional offset= and category= (Amazon Best Sellers by Category, Top Websites only).

Async

import asyncio
from trendsapi_app_store import AsyncTrendsAPI

async def main():
    c = AsyncTrendsAPI()
    return await asyncio.gather(
        c.get_time_series("com.openai.chatgpt"),
        c.get_time_series("com.openai.chatgpt", source="google search"),
    )

asyncio.run(main())

Each 200 is one billed request.

Pandas

from dataclasses import asdict
import pandas as pd
from trendsapi_app_store import TrendsAPI

df = pd.DataFrame(asdict(p) for p in TrendsAPI().get_time_series("com.openai.chatgpt"))
df["date"] = pd.to_datetime(df["date"])
print(df.set_index("date")["value"].resample("ME").mean().tail())

Call (curl)

FieldValue
EndpointPOST https://api.trendsapi.ai/api
AuthAuthorization: Bearer $TRENDSAPI_KEY
Historysource: app downloads with get_time_series or get_growth
KeywordAndroid bundle ID, e.g. com.openai.chatgpt (not chatgpt)
Live typeApp Store Top Free, App Store Top Paid, Google Play
curl -sS -X POST https://api.trendsapi.ai/api \
  -H "Authorization: Bearer $TRENDSAPI_KEY" \
  -H "Content-Type: application/json" \
  -d '{"mode":"get_time_series","source":"app downloads","keyword":"com.openai.chatgpt"}'

Source notes

  • chatgpt as keyword is 404. Use the Play Store id.
  • app downloads is Android history. iOS lists are live feeds only.
  • Live type values: App Store Top Free, App Store Top Paid, Google Play.

Errors

HTTPClient
200Parsed payload. Python dataclasses / JS typed objects
400Raises. Fix source or type spelling
401Raises. Check TRENDSAPI_KEY
404Raises. No series for that keyword. Do not retry
429Raises. Quota
5xxClient retries, then raises

The HTTP body field is a JSON string. SDKs decode it. Raw curl must parse body a second time.

Site: https://trendsapi.ai/trends/app-store-trends.

License

MIT. See LICENSE.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.