How to Scrape the Google Play Store (Apps, Reviews, Charts) in 2026
An unofficial Google Play API in one actor — search apps, pull full details and reviews, list top charts, mine autocomplete keywords, audit permissions. How the 10 endpoints work and what they return.
Google never shipped a public API for the Play Store. If you’re building an ASO tool, an app-analytics platform, or you just need to ingest a competitor’s reviews, your options have always been: scrape the HTML yourself and re-fix the parser every time Google reshuffles the page, or pay for an expensive data vendor. This guide covers a third option — treating the Play Store like the REST API it should have been, with endpoints for search, details, reviews, charts, and more.
An endpoint-shaped scraper, not a crawler
The mental model here matters. This isn’t a “give it a URL, get a page” crawler — it’s an unofficial REST-style API with ten endpoints, each answering a specific question:
- Search — apps for a query term.
- App details — full metadata for a package (batch lookups supported).
- Reviews — high-volume review scraping with pagination and sort options.
- Top charts — listings by collection and category.
- Similar apps — the “you might also like” graph.
- Developer — a publisher’s full portfolio.
- Autocomplete — keyword suggestions and their positions (the ASO goldmine).
- Permissions — declared Android permissions for an app.
- Data safety — the data-safety disclosure section.
- Categories — the category hierarchy.
It runs on pure HTTP (no browser), with sub-3-second cold start, concurrent batch lookups, and locale-aware retrieval so you can pull localized titles, ratings, and availability per market.
What app details return
The details endpoint is the workhorse. One package yields comprehensive metadata:
{
"appId": "com.example.app",
"title": "Example App",
"developer": "Example Inc.",
"developerId": "Example+Inc.",
"score": 4.3,
"ratings": 184203,
"rating_histogram": { "1": 4200, "2": 2100, "3": 9800, "4": 41000, "5": 127103 },
"installs": "10,000,000+",
"price": 0,
"free": true,
"iap": true,
"iap_range": "$0.99 - $99.99",
"version": "8.4.1",
"updated": "2026-05-19",
"content_rating": "Everyone",
"screenshots": ["https://...", "https://..."],
"icon": "https://...",
"description": "..."
}
Reviews come paginated and sortable (newest, most-relevant, by rating), each with text, score, author, app version, timestamp, and helpful-count — exactly what you need to stream large review volumes for sentiment and support analysis.
▶ Run the Google Play Data API scraper — 10 endpoints: search, details, reviews, charts, developer, autocomplete, permissions, data-safety. Pure HTTP, sub-3s cold start, locale-aware.
The ASO angle: autocomplete and charts
For app-store optimization, two endpoints do most of the work:
- Autocomplete returns keyword suggestions and their positions. Mining these tells you the real search phrases users type, and tracking position over time is the core of keyword-rank monitoring.
- Top charts by collection and category let you benchmark a category, watch new entrants, and track genre trends.
Combine autocomplete keyword mining with batch details lookups on competitors and you’ve reconstructed the data layer of a commercial ASO platform.
The compliance angle: permissions and data safety
The permissions and data-safety endpoints serve a different audience entirely — privacy and compliance teams. You can audit declared Android permissions and data-safety disclosures across a list of apps to flag over-reaching SDKs, surprising data collection, or apps that contradict their own privacy policy. Run it across an internal app inventory or a vendor list for an automated audit.
Typical use cases
- ASO platforms — track keyword rankings, mine autocomplete keywords, monitor competitor metadata changes.
- App intelligence & analytics — bulk-ingest app metadata, stream large review volumes, aggregate install and pricing signals.
- Market research — benchmark categories via top charts, track genre trends, map publisher portfolios via the developer endpoint.
- Privacy & compliance — audit permissions and data-safety disclosures across many apps.
- AI agents & LLM tools — feed app lists, reviews, and metadata into RAG and assistant tooling.
- Product teams — monitor reviews, version changes, and competitor releases for product and support insight.
Cost math
Pay-per-event: a small start fee plus roughly a tenth of a cent per result. Because it’s HTTP-only with fast cold starts, throughput is high and cost is low. Monitoring 50 competitor apps’ metadata daily plus a few thousand reviews lands in single-digit dollars a month. A heavy review-mining job — tens of thousands of reviews for sentiment training — scales linearly and stays cheap because there’s no browser or proxy overhead.
The DIY route is deceptively costly: the Play Store HTML is a moving target, the review pagination tokens change shape, and locale handling is fiddly. You’d be re-fixing parsers monthly. A maintained endpoint API absorbs that churn for you.
Pitfalls to plan for
- Installs are ranges. Google reports “10,000,000+”, not exact counts. Don’t treat them as precise.
- Reviews are locale-scoped. Reviews returned depend on the country/language you query — pull multiple locales for a global picture.
- Rate-limit your review depth. “All reviews” for a top-100 app is millions of records. Paginate to the depth you actually need.
- Autocomplete positions shift constantly. A single snapshot is a moment; track over time for rank trends.
- Package IDs are the stable key. Titles and developer names change with localization and rebrands — join on
appId. - Data-safety disclosures are self-reported. They reflect what the developer declared, not an independent audit — useful for compliance flags, not proof.
Wrapping up
The Play Store has no official API, so the value is in turning its scattered, HTML-buried data into clean, endpoint-shaped JSON. Whether you’re building ASO tooling, ingesting reviews at volume, or auditing permissions for compliance, a ten-endpoint unofficial API saves you from maintaining a fragile HTML parser and locale matrix forever.
▶ Open the Google Play Data API on Apify — search, details, reviews, charts, autocomplete, permissions and more. Pay per result. Start with Apify’s free monthly credit.
Related guides
App Store Data API Alternative: ASO Metadata Beyond iTunes
Apple's iTunes Search and Lookup API is rate-limited and thin. Here's an App Store data API alternative that returns full reviews, rankings, and keyword signals for ASO.
Binance Market Data Without API Keys: Spot Prices and Funding in 2026
How to pull Binance spot prices, order books and funding data without API keys — using the public REST surface, its weight limits and region blocks explained.
Binance Public API Endpoints: Klines, Depth & Funding Rate (No Key)
A reference for Binance's public market-data endpoints — klines/candlesticks, order-book depth, and futures funding rate — with exact URLs, parameters, rate-limit weights, and the data-api.binance.vision mirror. No API key required.