Google Play reference
Google Play API guide
Research an Android app using its package name and a consistent country/language pair, then read the available review pages.
Quickstart
Start with Google Play
Research an Android app using its package name and a consistent country/language pair, then read the available review pages.
These requests use your API key and can spend credits. Check the current price on the endpoint page; each new page is a separate request. Later examples use illustrative identifiers: replace them with values from your earlier response.
1. Find the app
Save the selected package name. Similar titles can refer to different apps. Parameters and current cost →
curl "https://www.monocrawl.com/v1/google_play/app-search?query=budgeting&country=gb&language=en" \ -H "x-api-key: mn_your_key_here"
2. Read the listing
Replace the example package with the selected result. Keep installs text separate from min_installs. Parameters and current cost →
curl "https://www.monocrawl.com/v1/google_play/app-info?package=co.uk.getmondo&country=gb&language=en" \ -H "x-api-key: mn_your_key_here"
3. Read review pages
Use the same package. Retain the returned cursor and keep filters unchanged. Parameters and current cost →
curl "https://www.monocrawl.com/v1/google_play/app-reviews?package=co.uk.getmondo&country=gb&language=en&sort_by=newest&limit=25" \ -H "x-api-key: mn_your_key_here"
Filters and coverage
Choose filters with the source behavior in mind
| Control | Behavior and limits |
|---|---|
| App identity | package is the Android package name or Play Store URL, not the App Store numeric ID. Keep country and language consistent. Endpoint reference → |
| Review selection | sort_by accepts newest, helpful or rating. rating is a local filter applied after fetch; retain the cursor even if filtering makes a page sparse. Endpoint reference → |
| Install and score fields | installs can be source text such as a range; min_installs is a lower bound when supplied. A store score and an individual review rating describe different populations. Endpoint reference → |
Source availability, ordering and field coverage can change. Inspect warnings and partial-result metadata alongside the rows. See runnable workflows, metric semantics, computed fields and the pagination matrix.
Choose an endpoint
Match the operation to your task
| Your task | Endpoint | When to use it |
|---|---|---|
| Store charts | app-list | Choose declared collection and category values. |
| Supported categories | categories | Google Play categories differ from App Store numeric genres. |
| Supported markets | locations | Market selection affects which listing or reviews you observe. |
Explore all documented operations by purpose below. Each endpoint reference contains its accepted parameters and current price.
Reviews and offers
Search and discovery
Products and categories
Operations
Google Play
Each row is a registry operation: expand it for parameters, a curl built from the registry's own examples, and a Markdown copy of the whole entry. The badge on the right is the operation's state, read at request time — we publish all three rather than rounding up. Recorded proof is historical, not a guarantee of current availability.
- live · proven
- a real upstream response has been served through this API and recorded
- wired · unproven
- a real-data route is registered, but qualifying proof is absent; permission or capacity restrictions may apply
- sample · free
- no live upstream — /v1 refuses it, /sandbox returns a marked sample
Google Play
8 operationsElsewhere
The same registry, other shapes
- Google Play overview — supported data categories and use cases for this platform.
- Full endpoint reference — every platform on one page.
/openapi.jsonor/openapi.yaml— the machine-readable contract, for Postman, Insomnia or a client generator.GET /v1/utility/endpoints?platform=google_play— the same rows to your code at runtime, for 0 credits.