App Store & Google Play Review Scraper — One Schema
Pricing
from $2.00 / 1,000 results
App Store & Google Play Review Scraper — One Schema
iOS and Android app reviews in ONE normalized format: stable IDs for dedupe, ISO dates, helpful counts, monitoring mode. No proxies needed.
Pricing
from $2.00 / 1,000 results
Rating
0.0
(0)
Developer
Nelliel
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
App Store + Google Play Review Scraper (one schema)
If you've ever pulled app reviews from both stores you know the problem. Apple hands you RSS XML with one set of fields. Google hands you something else entirely. The dates don't match, the rating fields don't match, and half your afternoon becomes a data-cleaning exercise instead of actual analysis.
This actor fixes that. You give it an app name — or both store IDs if you have them — and it returns iOS and Android reviews in one normalized JSON format. Same field names, same date format, same stable review IDs you can dedupe against across runs.
What you get
For each app: one summary record (name, rating, total ratings count, genre, developer, store URL) and then the reviews themselves:
{"review_id": "apple:14714962831","platform": "apple","rating": 5,"title": "Great for Teamwork","body": "New to Slack but loving it","author": "Gayle G","published_at": "2026-10-26T20:09:22Z","helpful_count": 0,"app_version": "26.10.30","developer_reply": null,"app": {"store": "apple","store_app_id": "618783545","name": "Slack","url": "https://apps.apple.com/us/app/slack/id618783545"}}
review_idis prefixed (apple:/google:) and stable — pull daily, dedupe locally, build your own history.- Dates are always ISO 8601 UTC.
helpful_count,app_version, anddeveloper_replycome through when the source feed carries them.
Example input
{"apps": ["slack", "notion", "duolingo"],"maxReviewsPerApp": 100}
Type a plain name and it resolves the right app on both stores (it checks the actual app title, so "Slack" won't accidentally grab "Slack for Intune"). Prefer certainty? Pass the exact IDs — numeric = App Store, dot-package = Google Play:
{"apps": ["618783545", "com.Slack"]}
Monitoring mode
Give it a since date and it only returns newer reviews — designed for a daily scheduled run that feeds a dashboard, an alert, or a spreadsheet:
{"apps": ["your.app.package"],"since": "2026-10-27","maxReviewsPerApp": 500}
Multi-storefront
Pass several country codes ("country": "us,de,fr") and it walks each storefront, deduping reviews by ID so you don't get repeats.
The honest limitations
I'd rather tell you these up front than have you find them at 2am:
- Apple's public RSS feed tops out around 50 recent reviews per storefront. That's an Apple limit, not mine — no actor can honestly get "all 54,000 Slack App Store reviews" from public endpoints. For Apple, think freshest reviews + monitoring, not full archive. Google Play pages deep, so Android gets full history (thousands of reviews).
- Apple's feed occasionally comes back empty for a specific app even when reviews obviously exist. When that happens the summary record says so explicitly (
reviews_returned: 0with a note) instead of quietly pretending the app has no reviews. Re-run later and it usually recovers. - Public endpoints only. Google's public review endpoint plus Apple's public RSS feed. If Apple's feed runs dry (it throttles datacenter IPs), the actor quietly retries through Apify's residential proxy — a few kilobytes per app. No stealth tooling; it can only ever get what the stores publicly publish.
Good fits
- Competitor review monitoring (ship a release, watch both stores' ratings react)
- Feeding a "what users hate this week" report to product teams
- Keyword alerts on new reviews (crash, paywall, refund...)
- Building launch-week comparison datasets
Pricing
Pay per result item — you only pay for records actually produced. A run of 3 apps × 100 reviews is roughly $0.60.
Something broken or a weird edge case? Message me on the actor's issues tab — I actually look at them.