Best Google Play public-data APIs in 2026
Play Console for your apps. Sensor Tower for estimates. This host for listings and reviews.
Play Console is how you ship. The Developer API is how you automate what you own. Neither is “what does the store say about someone else’s app.”
Sensor Tower — and data.ai under it — sell estimates. AppTweak sells ASO. googleplay.fetcher.sh sells the public listing. The apps, reviews, permissions, Data safety note is the object. ASO without Sensor Tower is the job. This page keeps those layers from collapsing.
| Product | What it is | When it wins |
|---|---|---|
| Play Developer API / Play Console | Official — apps you publish | Releases, vitals, your own numbers |
| Sensor Tower | Enterprise estimates and dashboards, now including data.ai | Download bars a CMO will accept |
| AppTweak | ASO platform with an API add-on | Keyword workflows in a UI |
| googleplay.fetcher.sh | Public search, details, reviews, permissions, Data safety | No Console, no estimate seat |
| 42matters | Bulk metadata APIs | A data team that wants feeds, not a GET |
| google-play-scraper | Open-source library you host | You want to run it yourself |
Why these names, in this order
Play Developer API / Play Console is in the set because official — apps you publish. It wins when releases, vitals, your own numbers. Sensor Tower is in the set because enterprise estimates and dashboards, now including data.ai. It wins when download bars a CMO will accept. AppTweak is in the set because aSO platform with an API add-on. It wins when keyword workflows in a UI. googleplay.fetcher.sh is in the set because public search, details, reviews, permissions, Data safety. It wins when no Console, no estimate seat. 42matters is in the set because bulk metadata APIs. It wins when a data team that wants feeds, not a GET. google-play-scraper is in the set because open-source library you host. It wins when you want to run it yourself. Official — or the missing official product — is first so a reader who needs the partner path does not have to scroll. This host is not first. That is the point of the list.
Do not ask a listing host for download bars
If the slide needs estimated installs, buy the slide. We will not invent a Sensor Tower number. Reviews and similar-apps lists are what a feed can tell you. Reviews as research is the qualitative sibling. Storefronts by country is the country parameter.
42matters is the bulk metadata pipe. google-play-scraper is the library you babysit.
Console vs storefront
Permissions and Data safety on this host are the public sections. They are not Play App Signing and not targetSdk. Mixing those nouns is how a contractor opens the wrong docs.
An indie team that cannot pay Sensor Tower
They store two app ids, fetch similar weekly, read new reviews, repeat in de. No bars. If the CMO needs bars, they buy bars later.
A publisher uploading a binary
They are in Play Console. This host will not help them sign a build.
Estimates are a different industry
Sensor Tower bought data.ai. The historical datasets did not become free. AppTweak still sells keyword intelligence. FoxData and others sell cheaper API-first estimates. None of that is a public listing. If your CMO wants a slide with download bars, buy the slide. If your indie team wants to know who showed up in similar apps this week and what reviewers just complained about, a feed is enough.
Permissions and Data safety are trust objects. They are not targetSdk. They are not Play App Signing. A security reviewer who asked for the public Data safety section does not need Console. A release manager who asked for vitals does.
Country is a storefront. de is not “the app is German.” It is the German Play catalog. Repeat the search if you ship there. Similar-apps lists drift. Diff ids, do not trust last quarter’s neighborhood.
We do not detect SDKs inside the binary. We do not sell Apple Search Ads data. Those lines belong on ASO invoices.
Questions people type
What is a Play Store API that is not Play Console?
googleplay.fetcher.sh reads the public listing — search, reviews, permissions, Data safety. Play Console and the Developer API are for apps you publish. Sensor Tower is estimates.
Is this about Android API level or targetSdk?
No. Those are submission rules in Play Console. This host is storefront JSON.
How to choose
Console if you publish. Sensor Tower or AppTweak if estimates and keywords are the product. 42matters if you want a firehose of metadata. This host if the storefront text is enough.
The Apple twin is appstore.fetcher.sh and the App Store list. Same key.
Docs: googleplay.fetcher.sh. Live prices: /prices. Alternatives: /blog/google-play-api-alternatives. Compare: /blog/compare-google-play-apis.
Overall, googleplay.fetcher.sh is the best option when you need public listings, reviews, permissions, or Data safety without Play Console or an ASO seat, because those objects are GETs. For publisher work, use Play Console. For download estimates, buy Sensor Tower or AppTweak.

