Google Play Reviews Scraper (app details, replies, no names)

Give the actor an app id (com.spotify.music) or a Play Store URL and get its reviews as flat rows — star rating, review text, date, helpful votes, the app version the review was written on, and the developer's public reply. Every row also carries the app card (name, developer, store rating, rating count, price, category), so app details and app store reviews come out of a single run. No login, no cookies, no reviewer names.

What you get

One row per review: id/reviewId, url, appId, appName, developer, appRating, appRatingCount, appPrice, appCurrency, appCategory, rating, text, reviewedAt, helpfulCount, appVersion, developerReply, developerRepliedAt, reviewerCountry, query, rank, source, scrapedAt.

url points at the single review (...details?id=<app>&hl=en&gl=us&reviewId=<id>), so every row is checkable by hand.

Example output

A real row (app com.spotify.music, sort: newest):

Field	Example value
appId / appName	com.spotify.music / Spotify: Music and Podcasts
developer / appCategory	Spotify AB / MUSIC_AND_AUDIO
appRating / appRatingCount	4.346 / 36289009
appPrice / appCurrency	0.0 / USD
reviewId	7a04c086-85ba-49c8-8b03-4cc4423b9020
rating / text	3 / can't listen offline
reviewedAt / appVersion	2026-09-11T19:38:27Z / 9.1.80.2221
helpfulCount	0
developerReply	Hi! We welcome your feedback. If you're on our free service, you can only enjoy music while connected to the internet...
developerRepliedAt	2026-09-11T19:52:42Z

Use cases

• Read what users complain about in your own app or a competitor's, filtered to 1-2 stars with minRating left open and sort: newest.
• Track how a release lands: appVersion on every review separates feedback on the new build from the old one.
• Audit support quality — developerReply and developerRepliedAt show which reviews the developer answered and how fast.
• Watch a set of apps in monitor mode and get an alert when new reviews or a changed developer reply appear.

How it works

1. The app's store page is fetched once per app id and the app card is read from its SoftwareApplication JSON-LD (name, developer, rating, rating count, price, category). An unknown app id answers 404 and is skipped, not counted as a block.
2. Reviews come from the same paged endpoint the Play web app itself calls, page by page with its own continuation token, until maxReviewsPerApp is reached.
3. An answer that is not a valid review page (a challenge, or a format change) is reported as a block instead of being pushed as an empty result.

Input

Field	Meaning	Default
appIds	App ids or Play Store URLs, e.g. com.spotify.music	["com.spotify.music"]
sort	newest, relevant or rating	newest
maxReviewsPerApp	Reviews read per app	100
minRating	Keep only reviews with at least this many stars (1-5)	empty
language / country	Play hl / gl, e.g. en / us	en / us
maxItems	Stop after this many rows in total	100
mode	scrape or monitor (only new/changed since last run)	scrape
monitorKey, webhookUrl, telegramBotToken, telegramChatId	Monitor-mode state key and alert targets	empty

Pricing

Event	Price
result	$0.0005 per review ($0.50 per 1,000)
monitor-check	$0.005 per monitor run
change	$0.0005 per new or changed review

You are charged only for rows actually pushed. A run that finds nothing charges no result events.

Why this actor

• App details and reviews in one run and one row — no second actor, no join on app id.
• The developer's reply and its timestamp are first-class fields, not buried in the review text.
• Monitor mode with webhook and Telegram alerts on new reviews, edited texts and new developer replies.
• No reviewer names, profile ids or avatars are collected, so the output is safe to keep and share.
• An empty run costs nothing and the RUN_SUMMARY record says why it was empty.

Limits

• Reviews are what Google Play serves publicly for the chosen language/country; other locales return other review sets. Play itself stops paging a few thousand reviews deep.
• reviewerCountry is always null — Play does not expose the reviewer's country. The column is kept so a dataset schema stays stable.
• No reviewer names, profile ids or avatar URLs, by design. If you need them, this actor is not for you.
• appRating is the current store rating of the app, not a per-review average, and it is the same on every row of that app.
• minRating filters inside the reviews read: with it set, the actor reads up to five times maxReviewsPerApp reviews while trying to fill the quota.
• Many Play reviews are stars only, with no words: text is then empty while rating, reviewedAt and appVersion are filled. Filter on text if you need written feedback only.
• The actor runs without a proxy (Apify's own egress), which is what Google Play currently answers. Under heavy parallel use Google may start rate-limiting that egress; switching the run to a datacenter proxy is then enough.

FAQ

Does it need a Google account or cookies? No. Everything is read as an anonymous visitor.

Can I get reviews in another language? Yes — set language and country (e.g. de / de). Play returns the review set for that storefront.

Why are there no reviewer names? Deliberate: the actor does not collect person-level data. Ratings, texts, dates and replies are returned; identities are not.

What happens when the app id does not exist? Play answers 404, the app is skipped and the run ends as no_matches with no charge, not as a block.

Changelog

• 0.1: initial release — app card plus reviews in one row, developer replies, sort and rating filter, monitor mode.

---

If this actor saved you time, a short review on its Store page genuinely helps other people find it. Found a bug or need a field that is missing? Open a ticket on the Issues tab.