Skip to content

Time series lookups

Time series endpoints return measurements for an entity over a date range. Use them to track performance, ratings, ranks, or SDK category performance.

Method Route Response fields
GET /api/:store/estimates App estimates
GET /api/:store/publisher_estimates Publisher estimates
GET /api/:store/app_sessions Sessions
GET /api/:store/ratings Ratings
GET /api/:store/app_ranks Ranks
GET /api/:store/app_ranks_summary Ranks summary
GET /api/:store/sdk_category_performance SDK category performance
Parameter Description
id or id[] Entity ID in the selected store. Repeat id[] for multiple IDs, up to 50.
date_from Start of the requested range, in YYYY-MM-DD format.
date_to End of the requested range, in YYYY-MM-DD format. Use at most 180 days per request.
country_iso ISO 3166-1 alpha-2 country code where the endpoint supports country-specific data, such as US.
model_version Estimates model, where supported: v2.0 or v3.0. See Model versions.

Use the entity ID appropriate for the endpoint: app IDs for app measurements, publisher IDs for publisher estimates, and SDK IDs for SDK category performance.

The result is a JSON array of matching measurements. This abbreviated app-estimates example shows the shape of a record:

[
{
"id": "com.facebook.katana",
"date": "2016-04-20",
"country_iso": "US",
"downloads": 64083,
"dau": 147883883,
"mau": 232027956,
"engagement": 0.6374
}
]

Available fields and historical coverage depend on the dataset and your account. To iterate through measurements across a dataset, use Time series discovery.

The presets use recent sample dates. Adjust the IDs, country, and dates to data available to your account.