Android app research
Use Google Play endpoints to turn android app research into repeatable API requests with documented inputs and JSON responses.
Build Android app intelligence workflows with structured Google Play data.
Collect Google Play app metadata, reviews, rankings, permissions, and search data.
Endpoint families
6
Documented params
59
Examples
11
Live catalog snapshot
Active endpoints
11
Methods
GET
Required params
20
Schema refs
11
{
"platform": "Google Play",
"endpoint": "googleplay-app",
"method": "GET",
"path": "/googleplay/app",
"auth": "apiKey"
}Related use cases
Free tools
Ready-made dataset
Crawlora has already indexed the full mobile app catalog — 2,113,447 on the Apple App Store and 2,950,482 on Google Play — with categories, ratings, pricing, install scale, and a cross-store popularity ranking. Browse the interactive data study and query it through the Datasets API.
Open the App & Google Play datasetUse cases
Collect Google Play app metadata, reviews, rankings, permissions, and search data.
Use Google Play endpoints to turn android app research into repeatable API requests with documented inputs and JSON responses.
Use Google Play endpoints to turn review ingestion into repeatable API requests with documented inputs and JSON responses.
Use Google Play endpoints to turn store ranking analysis into repeatable API requests with documented inputs and JSON responses.
Managed execution
Each Crawlora platform API is designed around a specific data surface. Instead of exposing a generic fetch endpoint, Crawlora combines endpoint-specific request logic, managed infrastructure, parsing, normalization, billing, and Playground-tested examples.
Request behavior is tuned for the target platform and endpoint type.
Supported endpoints can use managed proxy routing to improve reliability and reduce infrastructure work.
Dynamic pages can be routed through managed browser instances where JavaScript rendering is required.
Challenge pages and unusable upstream responses are detected and surfaced clearly.
Results are returned as documented JSON instead of raw HTML.
Test the same route from Docs and Playground before production integration.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/googleplay/app
/googleplay/categories
/googleplay/datasafety
/googleplay/developer/{dev_id}
/googleplay/list
/googleplay/permissions
Endpoint catalog
/googleplay/appReturns normalized app metadata from a Google Play details page, including installs, ratings, pricing, version info, developer metadata, media assets, release state, selected user comments, and "More by this developer" and "Similar apps" recommendation rails. For a per-device (phone/tablet/Chromebook) ratings-and-reviews breakdown, see `/googleplay/ratings`. Defaults: `country=us`, `lang=en`.
/googleplay/categoriesReturns category ids found in the Google Play apps navigation.
/googleplay/datasafetyReturns the data safety information displayed on Google Play.
/googleplay/developer/{dev_id}Returns apps published by a developer id or developer name.
/googleplay/listReturns apps from a Google Play collection and category.
/googleplay/permissionsReturns Google Play permission groups or a short permission name list.
/googleplay/ratingsReturns the ratings-and-reviews breakdown Google Play shows under the details page's device tabs, one entry each for phone, tablet, and Chromebook. Defaults: `country=us`, `lang=en`.
/googleplay/reviewsReturns one or more pages of app reviews. Set `paginate=true` to fetch only the requested page.
/googleplay/searchReturns Google Play search results for a term.
/googleplay/similarReturns apps from the "Similar apps" cluster on an app details page.
/googleplay/suggest/{term}Returns up to 10 suggestions for a search term.
Related APIs
App Stores
Collect Chrome Web Store extension discovery, listing, review, permission, and privacy signals as normalized JSON for app intelligence and browser-extension research workflows.
App Stores
Run App Store search queries and turn App Store listings, rankings, reviews, and developer pages into structured JSON for app intelligence, ASO research, and competitor monitoring workflows.
How to scrape Google Play
Google Play has no official public data API for listings, reviews, or rankings — only the Play Developer API for your own apps. Crawlora's Google Play endpoints return app metadata, reviews, permissions, data-safety, rankings, and search as structured JSON, without maintaining an Android scraper.
Run a Google Play search, browse a category or top-charts list, or target an app by its package ID.
Pass a query or app ID to Crawlora's Google Play endpoint (e.g. /googleplay/search, /googleplay/app, /googleplay/reviews).
Receive title, developer, category, installs, rating and review counts, permissions, data-safety details, and user reviews as clean JSON.
Feed Android app-intelligence and ASO dashboards, or re-run to track installs, ratings, and review trends over time.
FAQ
Send a search query or app package ID to Crawlora's Google Play endpoints and get app metadata, reviews, permissions, rankings, and search results as structured JSON — no Android scraper to maintain. Collect public data and respect Google's terms.
Google Play has no official public API for listings, reviews, or rankings — only the Play Developer API for apps you own. Crawlora covers app detail, search, categories, top-charts lists, permissions, data-safety, reviews, similar apps, and suggestions across public listings in one JSON shape.
Collecting publicly accessible app listing and review data is generally permissible if you respect Google's terms of use, robots directives, rate limits, and applicable law. This is for public data you are authorized to collect.