Google Play Reviews Scraper

Pull Google Play Store reviews for any app as clean, structured data. Give this Actor one or more app IDs and it returns the reviews: star rating, review text, author, date, thumbs-up count, the app version reviewed, and the developer's reply where there is one. One row per review, ready for a spreadsheet, a dashboard, or sentiment analysis.

What you get

For every app you submit, one dataset row per review with:

• app_id — which app the review belongs to (so you can scrape many at once).
• score — the star rating, 1 to 5.
• content — the review text.
• user_name and user_image — the reviewer's display name and avatar.
• at — when the review was posted (ISO 8601 timestamp).
• thumbs_up_count — how many people found the review helpful.
• review_created_version — the app version the review was written against.
• reply_content and replied_at — the developer's public reply, if any.

Example output

{
  "app_id": "com.spotify.music",
  "review_id": "58fd6e9a-1354-454c-9f3b-6e42b86c36c1",
  "user_name": "Satyam Jaiswal",
  "user_image": "https://play-lh.googleusercontent.com/a-/...",
  "score": 1,
  "content": "Playback keeps stopping when the screen locks",
  "thumbs_up_count": 12,
  "review_created_version": "2.26.35.75",
  "at": "2026-09-14T17:03:12+00:00",
  "reply_content": null,
  "replied_at": null
}

Input

Field	Type	Description
apps	array of strings	Required. One or more Play app IDs — the id= value in a store URL (for example com.spotify.music). One row per review, tagged with app_id.
sort	string	newest (default), most_relevant, or rating (highest first).
max_reviews_per_app	integer	Cap on reviews per app, paginated for you. Default 200, up to 20000.
lang	string	Review / interface language (en, de, fr, es…). Default en.
country	string	Store country (us, gb, de, nl…). Reviews are region-specific. Default us.

Where do I find an app's ID?

Open the app on Google Play and look at the address bar. The ID is the value after id=:

https://play.google.com/store/apps/details?id=com.spotify.music
                                              ^^^^^^^^^^^^

Common uses

• Product feedback and sentiment — pull the newest reviews for your app (or a competitor's) on a schedule and feed them into sentiment analysis.
• Release monitoring — filter by review_created_version to see how a specific release landed.
• Support triage — surface low-star reviews and whether they got a reply.
• Competitive research — scrape several rival apps at once and compare ratings, volume, and common complaints.
• Market research by region — run the same app across several country codes to compare how it is received in different markets.

How it is billed

Pay per result: you are charged once for each review returned, plus a small fixed charge when a run starts. An app with no reviews, or a bad app ID, returns no billable results and is reported in the run's error record. See the Pricing tab for the exact amounts.

Notes and limits

• Reviews are region-specific. The country you pick decides which store's reviews you see; run several countries to cover a global app.
• Sorting then capping. Reviews are ordered by your sort choice, then capped at max_reviews_per_app. newest plus a schedule is the usual way to keep an up-to-date feed without re-pulling everything.
• Developer replies are included inline on each review when present, so you do not need a second pass to see how the developer responded.
• One app that returns nothing does not fail the run — it is reported and the other apps still complete.

Tips

• Start with a modest max_reviews_per_app and a schedule; a daily newest pull keeps a rolling dataset cheaply.
• Scrape a set of competitor apps in one run by listing them all in apps; every row carries its app_id so they stay easy to split apart.