App Store Reviews Scraper Pro

Extract App Store reviews for any iOS app — author, star rating, headline, full text, date, helpful-vote count, and the app version reviewed. Any storefront country, newest-first or most-helpful order; filter by date range or rating range. Every app ends with a summary item that accounts honestly for what was fetched, emitted, and filtered, with the 1–5 star distribution of the result set.

The iOS twin of Google Play Reviews Scraper Pro — same inputs, same summary, same flat per-review pricing. Scrape both stores with one mental model.

Built for app developers doing ASO and review mining, support teams tracking complaints after a release, and market researchers comparing competitors' ratings over time.

Why this actor?

	App Store Reviews Scraper Pro	The App Store reviews niche
Price	Flat per review (see the Pricing tab) — no subscription	Mixed, mostly opaque per-run or subscription pricing
Small jobs	2,000 reviews cost pocket change, once	Minimums and monthly plans punish one-off jobs
Date range filter	Yes — start and end date, with early stop on newest sort	Rare
Rating range filter	Yes — min and max stars	Rare
Storefronts	Any country storefront in one run's inputs	Often US-only or one storefront per run
Per-app summary	Fetched / emitted / filtered + average rating + 1–5 star distribution	Usually absent
Minimums / start fees	None	Common

What it extracts (per review)

Field	Description
authorName	Review author's display name
rating	Star rating, 1–5
title	The review's headline
text	Full review text (null when Apple carries no body)
reviewDate	When the review was posted, ISO 8601 UTC
voteCount	How many users found the review helpful
appVersion	The app version the review was written against, when Apple knows it
reviewId	Apple's unique id for the review
appId	The numeric App Store id the review belongs to
country	The storefront the review was fetched from

Inputs

Input	Type	Default	Description
appIds	string list	—	Numeric App Store ids (324684580) and/or App Store URLs — the /id number is read from URLs
country	string	us	Storefront country (2 letters) — Apple serves each storefront's own review stream
maxReviewsPerApp	integer	100	Cap on reviews emitted per app, after filters (Apple's feed itself caps at ~500 per sort — see Honest limits)
sortOrder	select	mostRecent	mostRecent (newest first) or mostHelpful (helpful votes first) — the two orders Apple's public feed offers
reviewsStartDate / reviewsEndDate	date	—	Keep reviews inside this window (inclusive, UTC)
minRating / maxRating	number	—	Keep reviews inside this star range
includeSummary	boolean	true	Emit one summary item per app
proxyConfiguration	proxy	Apify Proxy	Standard Apify Proxy is normally enough; RESIDENTIAL is the fallback for repeated 403s

Outputs

Three item types share one dataset, told apart by the type field:

• review — one per review, fields as in the table above.
• summary — one per app: fetchedCount, emittedCount, filteredOutCount, averageRating, ratingDistribution (emitted reviews per star), and stoppedReason (resultsExhausted, maxReviewsReached, dateRangePassed, fetchSafetyCapReached, appFailed). The identity fetched = emitted + filtered always holds, so you can see exactly what your filters cost you.
• error — one per failed app, with the reason; if every app fails, the run itself is marked failed rather than returning an empty success.

Recipes

Release damage check. App: your own id. sortOrder: mostRecent, reviewsStartDate: the release date, maxRating: 2. You get exactly the angry reviews since the update, and the summary's distribution shows the damage shape.

Both stores, one spreadsheet. Run this actor and Google Play Reviews Scraper Pro on the same app, same date window. Same field names, same summary shape — the two datasets merge directly.

Local market pulse. Same app id, one run per storefront (country: fr, then de, then jp). Ratings and complaints differ by market; the per-app summaries compare directly.

Most helpful, not just newest. sortOrder: mostHelpful, maxReviewsPerApp: 100 — the reviews other users actually read, ranked by helpful votes.

FAQ

How much does a typical job cost? Pricing is flat per review with no subscription and no start fee — see the Pricing tab. 10,000 reviews across 5 apps is one run, one per-review charge, nothing monthly.

Can it get ALL reviews of a huge app? No — and nobody can from Apple's public feed: it exposes at most ~500 reviews per app per sort order (the 500 newest and the 500 most helpful). The summary tells you exactly how many were fetched. See Honest limits.

Why did my summary come back with 0 reviews? Either the app has no reviews in that storefront, or the app id doesn't exist there — Apple's feed answers both cases identically (an empty feed), so double-check the id and the country input.

Why is a review I see in the App Store missing? Reviews live per storefront. A review written in the French storefront is not in the US feed. Match the country input to the storefront you are looking at, or run once per storefront.

Does it need my Apple account? No. Reviews are read from Apple's public customer reviews feed; there is no login and nothing to connect.

Honest limits

• ~500 reviews per app per sort order, hard cap. Apple's public feed serves pages 1–10 only (50 reviews per page), for mostRecent and for mostHelpful. That is a window onto the app's most visible reviews, not its full history. The summary's fetchedCount states plainly how far the window reached.
• Per-storefront streams. The feed serves one storefront's reviews at a time. Reviews are never mixed across countries by Apple; scrape each storefront separately if you need several markets.
• No developer responses. The public feed does not include the developer's response to a review, so no reply fields exist in the output (the Google Play sibling has them because Play's backend carries them).
• Empty feed ambiguity. An unknown app id and an app with zero reviews in a storefront return the same empty feed from Apple. The actor reports a zero-count summary rather than guessing which case it was.
• reviewDate is the review's last-updated time — Apple exposes one timestamp per review in this feed (posting or last edit); there is no separate edit history.
• Apple occasionally reshapes its feed; the parser reads the feed's label fields defensively and emits null rather than guessing when a field is absent.