App Store & Google Play Reviews — Unified
Pricing
from $0.20 / 1,000 reviews
App Store & Google Play Reviews — Unified
Fetch normalized app reviews from BOTH the Apple App Store and Google Play in one schema. Aggregates across countries to blow past Apple's 500-review cap. For reputation monitoring and AI feedback analysis.
Pricing
from $0.20 / 1,000 reviews
Rating
0.0
(0)
Developer
Shawn Downs
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
Pull customer reviews from both the Apple App Store and Google Play in one normalized schema. Point it at an iOS app ID, an Android package, or both, and get clean JSON back — built for reputation monitoring, competitive research, and AI pipelines that summarize what users are saying.
Why this one
- Both stores, one schema. Apple and Google return wildly different shapes. This actor normalizes them into identical rows so you don't write two parsers.
- Beats Apple's 500-review cap. Apple's public feed hard-caps at ~500 reviews per
country. Pass a list of
countriesand the actor aggregates across all of them — an order of magnitude more reviews for global apps. - No auth, no scraping fragility. Apple's review RSS and Google Play's endpoints are public. Nothing to log into, nothing that breaks the moment a page redesigns.
Input
| Field | What |
|---|---|
appStoreId | Numeric iOS app ID (e.g. 310633997). Blank = skip Apple. |
playPackage | Android package (e.g. com.whatsapp). Blank = skip Google Play. |
countries | ISO codes; Apple aggregates across all of them. Default ["us"]. |
maxReviews | Cap per store. |
sortBy | recent or helpful. |
Output (per review)
store, app_id, country, review_id, rating, title, text, author, version, date, thumbs_up, vote_count, developer_reply, developer_reply_date, urlUnreachable stores return error rows — the run never fails.
Pricing
Pay per review returned (pay-per-event). Error rows are never charged.
Use with AI agents
MCP-friendly: an agent asks "what are people complaining about in v5.2?" and reasons over clean, cross-store JSON in one call — no per-store glue code.
