Google Play Reviews Scraper API — Filters & Insights

Why use this Actor?

Google Play reviews scraper for Android feedback intelligence. Find apps by name or package, export ratings, dates, text, helpful votes and developer replies; use multi-keyword/date/rating filters, app metadata, version/month/topic insights, proxy fallback and only-new monitoring.

Features

• Google Play apps — Direct package IDs or Google Play app URLs. Can be combined with appQueries.
• Maximum reviews per app — Maximum successfully emitted review rows for each unique app.
• Maximum total reviews — Hard result cap across all apps to keep runtime and spend predictable.
• Minimum rating — Only return reviews at or above this star rating.
• Maximum rating — Only return reviews at or below this star rating.
• Reviewed after — Optional inclusive lower date boundary. Use YYYY-MM-DD or ISO 8601.
• Reviewed before — Optional inclusive upper date boundary. Use YYYY-MM-DD or ISO 8601.
• Review text contains — Optional case-insensitive substring filter. Filtered rows are not billed.
• Minimum thumbs-up — Only emit reviews with at least this many Google Play thumbs-up votes.
• Developer reply — Return any reviews, only reviews with a developer reply, or only reviews without one.
• Maximum source pages per app — Safety ceiling for source pagination. Google Play returns up to about 200 reviews per page.
• Request timeout — Maximum seconds for each Google Play HTTP request.

Use cases

• Android app feedback research.
• Release monitoring.
• Support and product analytics.
• Review datasets for sentiment workflows.

Example input

{
  "appIdsOrUrls": [
    "com.spotify.music"
  ],
  "maxReviewsPerApp": 1000,
  "maxTotalReviews": 5000,
  "minRating": 1,
  "maxRating": 5,
  "minThumbsUp": 0
}

Pricing & cost control

Use the bounded input limits and filters to keep runs predictable. Pay-per-result Actors only charge primary result rows; summary, status and monitoring metadata are designed to add context without inflating result volume.

FAQ

What is this Actor for?
It is designed for Android app feedback research, release monitoring, support and product analytics.

Can I run it on a schedule?
Yes. You can schedule Actor runs on Apify and send the resulting dataset into automations, webhooks, storage, or downstream APIs.

How do I control cost and run size?
Use the input limits and filters shown in the Actor input form. The Actor applies bounded defaults and hard caps so large jobs remain predictable.

Search keywords

google play reviews scraper, google play scraper reviews_all, apify google play reviews scraper, outscraper google play reviews scraper, scrape google play store reviews, is google play trustworthy, does google play games save progress, play store reviews scraper, app store reviews scraper, google play store reviews scraper, google play store review scraper python, apple app store reviews scraper, scrape app store reviews, play

Extract public Google Play reviews from package IDs or app-detail URLs with clean normalized output, bounded retries, optional Apify Proxy fallback, deduplication, spend controls, and filters for stars, dates, text, thumbs-up votes, and developer replies.

The Actor is designed for production-style batches: one invalid or unavailable app produces a diagnostic row instead of crashing the entire run, duplicates are skipped, filtered reviews are not billed, and the run stops cleanly when the configured result or charge limit is reached.

What you get

Each successful row contains the package ID and canonical Google Play URL, review ID, reviewer display name and profile image when exposed, 1–5 star rating, review text, thumbs-up count, app version, UTC review timestamp, developer reply text/timestamp, and source/fetch metadata.

Input

appIdsOrUrls accepts package IDs such as com.spotify.music and Google Play app-detail URLs. Up to 100 apps can be submitted per run.

Useful controls include maxReviewsPerApp, maxTotalReviews, minRating / maxRating, reviewedAfter / reviewedBefore, containsText, minThumbsUp, developerReply, maxPagesPerApp, request timeout/retries, and proxy controls.

Example

{
  "appIdsOrUrls": [
    "com.spotify.music",
    "https://play.google.com/store/apps/details?id=com.whatsapp"
  ],
  "maxReviewsPerApp": 500,
  "maxTotalReviews": 1000,
  "minRating": 1,
  "maxRating": 3,
  "reviewedAfter": "2026-01-01",
  "containsText": "",
  "minThumbsUp": 0,
  "developerReply": "any",
  "maxPagesPerApp": 25,
  "autoProxyFallback": true,
  "proxyConfiguration": {"useApifyProxy": false}
}

Reliability behavior

Google Play's public review endpoint is unofficial and can change, so the Actor avoids unbounded requests and silent failures. HTTP rate limits, server failures, and transport errors use bounded retry/backoff. Direct access is attempted first; when it fails and automatic fallback is enabled, one retry path uses a fresh Apify Proxy session.

Duplicate package IDs and review IDs are removed. Invalid inputs and source failures create uncharged diagnostic rows instead of terminating the entire batch. Source-page, per-app, and global result ceilings prevent accidental unbounded crawling.

Important note about country and language

Google Play public reviews are returned as a global review corpus by this source. The store presentation locale is not the reviewer's country, and this feed does not expose a trustworthy reviewer-country field.

For that reason this Actor intentionally does not offer a misleading "review country" filter or claim to infer a reviewer's location.

Filtering and scan window

Star and date filters are applied while walking newest-first source pages. Text, thumbs-up, and developer-reply filters depend on fields in each returned review. When any of those filters is enabled, the Actor automatically scans beyond the requested output count, bounded by maxPagesPerApp, so selective filters still have room to find matches.

A very selective filter plus a small page ceiling can legitimately return fewer rows than maxReviewsPerApp.

Output

Successful rows use recordType: "review" and include:

• appId, appUrl, reviewId
• userName, userImageUrl
• rating, text, thumbsUpCount
• reviewCreatedVersion, reviewedAt
• hasDeveloperReply, developerReplyText, developerRepliedAt
• source, fetchedAt, scan/runtime diagnostics

Failures use recordType: "error" and are not billed.

Billing

The launch target is $0.00009 per successful review — about $0.09 per 1,000 results — plus the minimal Actor-start event configured in Apify.

Only successful review rows trigger the custom review charge event. Invalid inputs, retries, source failures, duplicate inputs, and reviews rejected by filters are not charged. The Actor checks the Apify charge limit while writing results and stops cleanly when the budget is exhausted.

Limits

• 100 app inputs per run
• 50,000 emitted reviews per app
• 100,000 emitted reviews per run
• 250 source pages per app
• public Google Play review data only
• no login bypass, private-data access, or reviewer-location inference

Google Play can change its public web responses without notice. A successful scrape reflects the public data exposed at run time, not a guarantee that every historical review remains reachable indefinitely.

Responsible use

Use public review data in accordance with applicable laws, privacy and data-protection requirements, and platform terms. Avoid using reviewer data for harassment, sensitive profiling, or attempts to identify people beyond what they publicly posted.

Support

For a reproducible issue, provide the public package ID or Play Store URL, relevant filters, proxy mode, and Apify run ID. Never include API tokens or private proxy credentials.

Extended capabilities

• Resolve apps by Google Play search query or accept package IDs / app URLs directly.
• Add public app metadata such as developer, category, price, version, rating, icon, and release/update dates.
• Sort reviews by newest, oldest, or rating and monitor unseen reviews with aggregate intelligence.