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
54
Examples
10
Live catalog snapshot
Active endpoints
10
Methods
GET
Required params
18
Schema refs
10
{
"platform": "Google Play",
"endpoint": "googleplay-app",
"method": "GET",
"path": "/googleplay/app",
"auth": "apiKey"
}Related use cases
Ready-made dataset
Crawlora has already indexed the full mobile app catalog — 1,170,541 on the Apple App Store and 2,938,575 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, and selected user comments. 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/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