The direct answer:the Google Play Developer API's Reviews resource is a support tool for developers managing their own apps — and for that job it is the right, official tool, and the only one in this comparison that can replyto a review. For apps outside your Play Console, the Play Developer API has no endpoint: the Reviews resource is scoped to apps the authenticated Play Console identity is authorized to manage, returns only reviews that include text, and only those created or modified within the last week. For competitor research, market analysis, or any public app's listed review history, the working route is a scraper such as the Google Play Reviews Scraper.
This page contains no Developer API run: exercising the Reviews resource requires a Play Console identity authorized on a published app, and its permission scope is not observable from outside. Every claim about the Developer API below links Google's own documentation, all verified on 2026-07-21. The actor side was run first-hand on 2026-07-21 against a third-party app — the run and its evidence file are below.
The Play Console permission gate, per Google's docs
- Google's Reply to Reviews guide states the API "allows you to access feedback only for production versions of your app." The boundary is Play Console permission, not legal ownership — invited users and service accounts qualify — but there is no parameter, scope, or quota tier that reads an app outside the accounts the authenticated identity is authorized on. Arbitrary public apps are out of reach by design.
- Setup, per the getting-started guide: create a Google Cloud project, enable the Google Play Developer API, create a service account (or OAuth client), then invite that identity as a user of the Play Console account with the necessary permissions. Four steps across two consoles before the first request — reasonable for a developer-side integration, and unavailable without Play Console access to the app.
Two documented limits that surprise even owners
The same Reply to Reviews guide documents two limits that apply even to your own app. First, the window: "You can retrieve only the reviews that users have created or modified within the last week." The API is a rolling seven-day feed, not an archive. Second, the text filter: "the API shows only the reviews that include comments. If a user rates your app but does not provide a comment, their feedback is not accessible from the API." Star-only ratings never appear.
For full history of your own app, Google's documented route is not the API but the Play Console's monthly review reports: CSV files in a private Google Cloud Storage bucket, captured daily and "posted within 3 to 7 days," gated by the same Play Console access restrictions. So even a developer combining both official tools gets a seven-day live window plus monthly CSVs on a multi-day lag.
The decision, by dimension
| Dimension | Play Developer API Reviews resource | Google Play Reviews Scraper |
|---|---|---|
| Apps it can read | Apps the authenticated Play Console identity is authorized to manage, production versions only. Google documentation. | Any app with a public Play Store listing. apihq documentation; demonstrated for one third-party app in the run below. |
| Auth required | Google Cloud project + service account or OAuth client, invited into the app's Play Console. Google documentation. | Apify API token. By design — Apify platform auth. |
| Review history | Reviews created or modified within the last week; older history only via monthly CSV exports on a 3–7 day posting lag. Google documentation. | Walks the public listing's review pages until your maxReviews cap or the app runs out. apihq documentation; the run below delivered reviews with posting dates back to 2024-08-28. |
| Star-only ratings (no text) | Excluded — "not accessible from the API." Google documentation. | Returns the public listing's review set; the text field may be empty. apihq documentation; not independently tested. |
| Replying to reviews | Yes — reviews.reply, the only option in this comparison that can post developer replies. Google documentation. | No. By design — the actor is read-only. |
| Cost | No per-request price listed; Google documents quota limits instead (default 3,000 queries per minute per quota bucket). Google's quota page. | $0.08 per 1,000 delivered reviews; failed items $0. apihq list pricing. |
| Terms-of-service posture | Official API, unambiguous. First-party assessment. | Reads public data outside the official API; not affiliated with or endorsed by Google. First-party assessment. |
When the Developer API is the better choice
- Responding to reviews of an app you manage — it is the only option in this comparison that can post developer replies, and support tooling built on it can catch a bad review within its seven-day window.
- Live monitoring of your managed app's fresh text reviews: no per-call charge listed, a generous per-minute quota, and an official surface.
- Full history of an app you manage when a monthly CSV on a 3–7 day lag is acceptable — the Play Console's own reports, straight from Google.
- Workflows that must stay inside Google's official API surface for compliance reasons.
When the actor is the better choice
- Reviews of apps outside your Play Console — competitor apps, market category scans, churn research. The Play Developer API has no endpoint for arbitrary public apps; the permission scope is the product design, not a limit you can raise.
- Review history deeper than seven days, on demand, without waiting for a monthly CSV: one run walks the public listing's pages back as far as they go.
- Pipelines without a Google Cloud project: one HTTP call with an Apify token from a script, n8n, Make, or a scheduled workflow, with typed, unbilled failure rows instead of per-project credentials to manage.
- Cost certainty on batch jobs: $0.08 per 1,000 delivered reviews, and an app with no reviews returns an unbilled
success: falserow while the batch keeps going.
The first-hand actor run, as evidence
On 2026-07-21 at 12:00 UTC we ran the Google Play Reviews Scraper (build 0.1.2) once against com.spotify.music with sort: relevance and maxReviews: 200 (Apify run 4JpCN5ewo2BWmppj8). The run finished SUCCEEDED in 39 seconds and delivered 200 success: true review rows. The oldest review carries a posting date of 2024-08-28 — roughly 23 months before the run — and 178 of the 200 were posted before 2026-07-14 00:00 UTC. The run emitted 200 review charge events; at the public list price of $0.00008 per review that is $0.016 (we ran our own actor, so this is a list-price value, not an observed customer charge).
One deliberate limit on that reading: Google defines the Developer API window as reviews "created or modified within the last week," and our data records posting dates only. An old review that was recently edited could still appear in the API, so the run does not prove that any specific row would be excluded from it — only that the actor returns reviews posted long before any seven-day span.
The full run output, sanitized — review text bodies, reviewer names, and avatars removed; IDs, dates, ratings, and text lengths retained — is published at /evidence/google-play-reviews-run-2026-07-21.json with the run's metadata (timestamps, build, dataset ID, charge counts), and any row can be checked against its public Play Store permalink by review ID. Two different evidence classes apply here. Test result: the actor delivered 200 Spotify reviews with the posting dates recorded in the artifact. First-party disclosure: apihq holds no Play Console authorization for Spotify — Play Console permission state is not externally verifiable, so take that claim as a disclosure, not a measured result. And it is one run against one app on one date — not a reliability or coverage statistic.
Methodology and sources
- No first-hand Developer API run:the Reviews resource is scoped to apps the authenticated Play Console identity is authorized on, so this page relies on Google's documentation — linked at every claim and re-checked on the last-verified date above — rather than a test we could only run against an app we published ourselves.
- Actor rows: pricing, output fields, and failure behavior come from the actor's documentation, the canonical copy for this site — it currently includes corrections not yet synced to the Apify listing; the sync is queued. Delivery of a third-party app's reviews with posting dates back to 2024 is demonstrated by the first-hand run above (our lack of Play Console authorization for that app is a first-party disclosure); the remaining actor rows are documentation claims, reproducible with one run.
- Corrections:if Google's documented behavior changes or a row is wrong, use the support and corrections route; the page carries its last-verified date at the top.