App Store Review Scraper & Feedback Monitor

Build an ongoing stream of new and edited iOS app reviews, with star ratings, review text, app versions and country storefronts. Watch your own app or a competitor and send the structured output to a product-feedback database, n8n, Make or an AI analysis workflow.

The Actor also checks Apple's app metadata: current version, store average rating and rating count. These store-wide figures are separate from the average of the reviews returned in this run.

Who this is for

iOS product feedback and low-star review monitoring. Use the App Store review scraper to collect public iOS feedback by storefront, app version and rating. Connect newly observed or edited reviews to a product-feedback database. Review-window metrics and store-wide ratings are reported separately.

Quick start

For an immediate export:

{
  "apps": ["324684580"],
  "countries": ["us", "es"],
  "maxReviewsPerCheck": 100,
  "outputMode": "all"
}

Monitor negative feedback on a schedule:

{
  "apps": ["324684580"],
  "countries": ["us"],
  "maxReviewsPerCheck": 200,
  "maxRating": 2,
  "watchId": "app-complaints",
  "outputMode": "changes"
}

In changes mode, the first successful run establishes a baseline without review alerts. Later runs with the same Watch ID emit new or edited reviews, and changed app metadata. A review edited from five stars to one star can trigger an alert even when the original five-star review was filtered out. Star filters affect output only, so all scanned reviews are remembered.

App Store URLs are accepted alongside numeric IDs. Countries are selected explicitly in countries; a country embedded in a pasted URL does not override that list. Duplicate IDs and country codes are removed. At most 20 unique app-country pairs can be checked per run.

Output

• recordType=review: reviewId, appId, appName, country, rating, title, text, appVersion, updatedAt, publicReviewerName, appUrl, changeType, changedFields, previousRating and observedAt.
• recordType=app: current app metadata, changed fields, previous version and previous store rating/count. App records are unaffected by star filters.
• recordType=check_summary: health, pages checked, reviews scanned, baseline/new/changed/unchanged counts and store rating snapshot. Summaries are always included.
• recordType=source_error: failed source checks; the previous history is preserved. SUMMARY in the default key-value store contains the overall run report and spending-limit status.

The public review's updatedAt is Apple's timestamp; it may describe an edit rather than the original publication date. new means newly observed by your watch. The tool reports review changes; it does not generate sentiment labels or send replies to reviewers. Store rating changes also include star-only ratings, which the written-review feed does not expose.

Pricing

$0.025 per successful app-country check, including app metadata and up to 500 recent reviews, plus $0.00005 per run start at fixed 512 MB memory. Platform usage is included. There is no per-review or per-summary charge.

An app checked in three countries is three checks. Empty or unchanged review feeds still count when the app lookup and requested feed pages succeed. Failed checks do not trigger the app-country event. A failure after an earlier page causes the entire check to fail without replacing history or charging the check event. The standard start fee still applies.

Example: five apps in two countries cost $0.25005 per run, or $7.5015 if run daily for 30 days. These are buyer costs, not creator earnings. Use Maximum cost per run to stop before additional app-country checks exceed the event budget.

Limits and history

Apple's public review feed provides a recent window, commonly up to ten pages of fifty reviews per app-country. This Actor scans the number of pages needed for your review cap, including later pages after an empty middle page, and deduplicates repeated review IDs. Pagination can change while a run is in progress, so this is not a guaranteed complete archive.

maxReviewsPerCheck defaults to 100 and ranges from 1 to 500. Reviews not scanned are not added to history. Increasing the cap can therefore surface older reviews as newly observed. Missing reviews are not classified as deleted. Reviews may disappear from the feed or fall outside its window.

Watch history retains review IDs and comparison hashes for 90 days since last observation, with a 20,000-ID cap per app-country. Full historical review bodies are not retained in the named watch store. Use the same Watch ID for non-overlapping schedules; a new ID resets history. Snapshots live in the caller's account. Do not run the same watch concurrently.

Only public iOS App Store data is read. No Apple account, App Store Connect key, cookies or proxy is required. Unavailable apps or unsupported country codes produce errors. Developer replies and private support messages are not part of the feed. This independent tool is not affiliated with Apple.

Source: Apple's public itunes.apple.com review feed and iTunes lookup API.

Related tools: ATS Job Watch, Shopify Price & Restock Watch, and WordPress Content Watch.

Try one source before scheduling

1. Open the Input tab and use one supported source with outputMode: "all" for an immediate export.
2. Check the returned records and the check summary. Confirm the source, coverage and price suit your workflow.
3. To monitor, set a stable Watch ID and outputMode: "changes". The first successful run establishes a silent baseline.
4. Reuse that Watch ID on later runs. A summary without change records means the check completed without matching changes.
5. Add an Apify schedule after the manual checks work. Avoid overlapping runs with the same Watch ID. Use Maximum cost per run to cap event charges.

Public-data monitors by the same developer: browse the catalog.