Price
| Metrics | Comment | Credits/app/keyword for 1 day | Credits/app/keyword per extra day |
|---|---|---|---|
| rank | Ranking of an app for a keyword. | 10 | 1 |
| installs | The estimated number of daily installs driven by a keyword to an app. | 10 | 1 |
Ranked, unranked or no dataTo know whether your app is ranked on a keyword or not, you can refer to the following logic in the response data:
•
value= non-null andfetch_performed=true➔ ranked
•value=nullandfetch_performed=true➔ unranked
•value=nullandfetch_performed=false➔ no dataIn addition to
value, you can useeffective_value, that corresponds to a value that is guaranteed to be non-null. The logic to computeeffective_valueis:• If
valueis notnull,effective_value=value
• Otherwise, iffetch_performed=true, theneffective_value=501, the numeric representation of unranked
• Otherwise, if there is at least one non-null value in the date range, take the closest day to the missing day and use thatvalue(an average if two days are equally close)
• Otherwise, defaults to501
Improved Keyword Installs starting July 17, 2025Starting July 17, 2025, we're updating our keyword installs estimates. This change will make keyword performance trends even more precise, especially when looking at historical data.
effective_valuecan differ between requests for the same day
effective_valueis estimated using the other days within the date range you queried — it never looks outside yourstart_date/end_date. This means that querying the same day with a wider or narrower range can return a differenteffective_valuefor that same day, if it changes which neighboring days are available to estimate from.If you need a number for a given day that's stable regardless of the range you query, use
valueinstead, and treat null as "no estimate available" rather than defaulting it to 0 yourself.More info on these rule can be found here.
Unauthorized. Unknown or missing API token.
Forbidden. Not enough credits to perform the request.
Validation error. Returned when a parameter is invalid.