App Store & Google Play Reviews API
Pricing
from $0.06 / 1,000 reviews
App Store & Google Play Reviews API
iOS App Store and Google Play reviews as one JSON stream: rating, title, text, app version, date, helpful votes, developer replies, country and language. Both stores in one actor, from $0.09 per 1,000 reviews.
Pricing
from $0.06 / 1,000 reviews
Rating
0.0
(0)
Developer
subimpact
Maintained by CommunityActor stats
0
Bookmarked
3
Total users
2
Monthly active users
a day ago
Last modified
Categories
Features
Share
Pull iOS App Store and Google Play reviews as one clean JSON stream. One row per review with the rating, title, text, app version, date, helpful votes and developer reply — from both stores, in the same run, from the same input list.
- Both stores, one actor. Paste App Store URLs/ids and Google Play URLs/package names together; the store is detected per app.
- No login, no API key, no account risk. Reads the public review feeds the two stores serve to their own web pages.
- Deep paging. Google Play pages through its review RPC with continuation tokens (thousands of reviews per app). Apple goes up to 500 reviews per app from the sorted public feed, and past 500 through Apple's own deeper web endpoint.
- Priced per delivered review. Only real review rows are charged: reviews you filter out, apps that return nothing, and error rows cost nothing.
What you get
| Stores | Apple App Store, Google Play |
| Unit | one dataset item per review |
| Freshness | the store's own feed — reviews published minutes ago are usually there |
| Filters | country, language, sort order, star-rating range, “since” date, per-app cap |
| Volume | up to 50,000 reviews per app, as many apps as you paste |
Quick start
Input:
{"apps": ["id389801252", "https://play.google.com/store/apps/details?id=com.instagram.android"],"country": "us","language": "en","sort": "newest","maxReviewsPerApp": 200}
Run it (or click Start with the same input):
$apify call YOUR_USERNAME/app-reviews-api --input '{"apps":["id389801252","com.instagram.android"],"maxReviewsPerApp":200}'
Accepted app references (mix and match in apps):
id389801252,389801252,https://apps.apple.com/us/app/instagram/id389801252com.instagram.android,https://play.google.com/store/apps/details?id=com.instagram.android
An entry that cannot be read is reported as an uncharged error row, and the rest of the run continues.
Input
| Field | Type | Default | What it does |
|---|---|---|---|
apps | array | — (required) | App Store URLs/ids and/or Google Play URLs/package names. Duplicates are collapsed. |
country | string | us | Two-letter store country (us, gb, de, my, sg, in, jp, br…). Decides which reviews exist: Apple storefront, Google Play country. |
language | string | en | Language used for the store pages (en, de, pt-BR, zh-Hans…). Review text is always returned exactly as the reviewer wrote it. |
sort | string | newest | newest or mostRelevant (the store's own relevance / most-helpful order). |
maxReviewsPerApp | integer | 200 | Cap on delivered reviews per app, 1–50,000. The default keeps a run at about two cents. |
minRating / maxRating | integer | — | Keep only reviews inside a star range (1–5). Filtered reviews are never charged. |
sinceDate | string | — | Only reviews published on or after this ISO date, e.g. 2026-01-01. With sort=newest the run stops paging as soon as it reaches older reviews. |
Output
One dataset item per review. This is a real row from a live test run (Instagram, us, 2026-11-15):
{"store": "apple","appId": "389801252","appName": "Instagram","reviewId": "14785061938","userName": "edesland","rating": 1,"title": "complain","text": "I used to enjoy sharing photos and memories on Instagram. About a year ago, Meta closed my Instagram and Facebook accounts without an explanation I could understand. I opened a new Instagram account, and now I can’t change the password. The saved password is rejected, and tapping “Forgot your password?” immediately brings up “Something went wrong, please try again.”\n\nI’m still signed in on my phone, but I’m afraid to rely on Instagram for photos I care about. If I lose access again, I don’t know how I’ll get them back. I haven’t found a support option that helps me resolve this. Meta needs a password reset that works and a way to reach someone when it fails.","version": "455.0.0","date": "2026-11-13T10:57:47.000Z","thumbsUp": 0,"developerReply": null,"developerReplyDate": null,"country": "us","language": "en","scrapedAt": "2026-11-14T19:32:31.672Z","status": null,"error": null}
A Google Play row from the same run, for comparison:
{"store": "google","appId": "com.instagram.android","appName": "Instagram","reviewId": "fd12ca1f-d50d-40aa-9ff1-2fc101ef1a12","userName": "Tayoubi Sara","rating": 1,"title": null,"text": "I don't have the repost bottom and I can't see who likes the reels even when I update the app","version": null,"date": "2026-11-13T19:31:21.000Z","thumbsUp": 0,"developerReply": null,"developerReplyDate": null,"country": "us","language": "en","scrapedAt": "2026-11-14T19:32:31.672Z","status": null,"error": null}
Field reference
| Field | Type | Source |
|---|---|---|
store | string | apple or google, detected from the app reference |
appId | string | Apple numeric id, or Google Play package name |
appName | string | Apple: iTunes lookup trackName. Google: the Play page title |
reviewId | string | Apple review id / Google review id — stable, usable as a primary key |
userName | string | reviewer's public display name |
rating | integer | 1–5 stars |
title | string | review title; null for Google Play (Play has no review titles) |
text | string | full review body, line breaks preserved |
version | string | app version the reviewer was running. null when the reviewer hid it, and on the Apple deep path (>500 reviews), where Apple does not publish it |
date | string | review publication time, ISO 8601 UTC |
thumbsUp | integer | Google Play helpful-vote count; Apple helpful votes when Apple publishes them |
developerReply | string | developer response text — Google Play only (Apple's public review feeds carry no developer responses) |
developerReplyDate | string | developer response time, ISO 8601 UTC |
country / language | string | the store country and language this run used |
scrapedAt | string | when this row was collected |
status / error | string | set only on uncharged non-review rows (bad app reference, store failure) |
Pricing
$0.09 per 1,000 reviews ($0.00009 per delivered review), platform usage included. You pay only for review rows that land in your dataset: filtered-out reviews, empty apps and error rows are free. A default run (2 apps × 200 reviews) costs about $0.04, a 10,000-review pull about $0.90.
Charging stops automatically at your account's maximum charge per run — the actor then stops collecting instead of delivering rows you were not charged for.
How it works, and what it cannot do
- Apple reviews come from Apple's public customer-reviews feed (50 reviews per page, 10 pages =
500 reviews per app), which is the only Apple source that can be sorted by date/relevance and that
exposes the app version. If you ask for more than 500 reviews for an app, the actor switches to the same
deeper endpoint
apps.apple.comuses for its own review list, which pages past 500 but returns Apple's own ordering and no app version. - Apple publishes no developer responses on those endpoints, so
developerReplyanddeveloperReplyDateare null forstore: "apple". - Google Play reviews come from the store's own review RPC, paged with continuation tokens, so volume
is not limited to what the app page embeds. Play has no review titles, and some reviewers hide their app
version — that is when
versionis null on a Play row. - Sort order:
mostRelevantis the store's own relevance ordering, which is not chronological. Usenewest(the default) when you need recent reviews or asinceDatecutoff. - Rate limits: both endpoints are public and served without keys. The actor paces requests, retries with backoff on 429/5xx, and — if a store starts blocking its IPs — retries through a datacenter proxy. Very large runs (>10,000 reviews) are best split into several runs by app.
- Reviews are public data, but treat reviewer names as personal data under GDPR if you store them.
Support
Found a store change, a field that stopped filling, or need another market? Open an issue on the actor's page — store feed changes are fixed quickly.