📱 App Store Reviews Scraper — All Countries, Filters, Replies

Scrape Apple App Store reviews for any iOS app — by app ID, App Store URL or a search term — across one or many countries in a single run. Each row carries the rating, title, text, app version, date, author handle and the developer's reply. Filter by star rating, keywords, developer-reply state, a date range or the last N days before anything is billed. Watch mode on a schedule delivers only new reviews.

• Many storefronts at once: countries: ["us","gb","de","jp"] reads each country's feed (up to 500 reviews per app per country, the public feed's limit).
• Rolling window: recent_days: 7 on a daily schedule gives you only the last week's reviews.
• No login, no API key, no CAPTCHA solving: Apple's public review feeds, read logged-out.

Output is one row per review; billing is pay-per-event, the value event being one review scraped (a $0.02 start fee per run, then $0.0013 per review scraped). Source: itunes.apple.com.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out.

Who buys this

Buyers usually search for App Store reviews or iOS app reviews.

• Product, ASO and app-marketing teams tracking App Store reviews.
• Analysts and agencies benchmarking competitors with iOS app reviews.
• Data teams feeding app data into dashboards and BI.

📊 Sample Output

Real rows from run 89PPVoRLVT3Feo1UW on build 0.1.34 (2026-09-28), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

app_id	review_id	title	author_handle	review_date	collected_at
284882215	14599347161	I had to give a review	Heisnelson1	2026-09-27T05:27:52-07:00	2026-09-28T20:50:32.315869+00:00
284882215	14599373434	Good for humanity!	jaypique	2026-09-27T05:36:22-07:00	2026-09-28T20:50:32.315866+00:00
284882215	14599384049	Loving your customers	MadelineSanchez	2026-09-27T05:39:45-07:00	2026-09-28T20:50:32.315862+00:00
284882215	14599396744	I loved it	Dahalsomsanita	2026-09-27T05:43:44-07:00	2026-09-28T20:50:32.315859+00:00
284882215	14599404276	I LUV FACEBOOK	Hamad Alrabiah	2026-09-27T05:46:07-07:00	2026-09-28T20:50:32.315856+00:00
284882215	14599422823	Give Us Back the Ability To See All Comments	J-Dawn	2026-09-27T05:51:59-07:00	2026-09-28T20:50:32.315853+00:00
284882215	14599439140	It great	Blueshepherd💙	2026-09-27T05:57:03-07:00	2026-09-28T20:50:32.315850+00:00
284882215	14599440425	Awesome Food	Mhjubilee	2026-09-27T05:57:26-07:00	2026-09-28T20:50:32.315848+00:00

The run finished with the status message: SUCCEEDED: emitted 25 item(s)

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

• store (string/null) — Output field: store
• app_id (string/null) — Output field: app_id
• review_id (string/null) — Output field: review_id
• title (string/null) — Output field: title
• review_text (string/null) — Output field: review_text
• rating (number/null) — Output field: rating
• author_handle (string/null) — Output field: author_handle
• review_date (string/null) — Output field: review_date
• version (string/null) — Output field: version
• developer_response (string/null) — Output field: developer_response
• developer_response_date (string/null) — Output field: developer_response_date
• country (string/null) — Output field: country
• source_url (string/null) — Output field: source_url
• collected_at (string/null) — Output field: collected_at

What you get

• Public Apple App Store review entries: rating, title, review text, author, date, and app version
• Developer responses and response dates where present
• A normalized 14-field record per review with source URL and collection timestamp
• Bounded retries with explicit block / gone outcomes — you always know if zero means empty or blocked
• Optional watch mode that emits only new reviews and status changes on later runs

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
  "app_ids": [
    "284882215"
  ],
  "country": "us",
  "language": "en",
  "max_items": 10,
  "watchMode": false,
  "sort": "most_recent"
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 25 × $0.0013 review-scraped + 0 × $0.10 watch-check = $0.0525 on the Free tier — every delivered row was billed.

2. A smaller, narrowed run

{
  "app_ids": [
    "284882215"
  ],
  "country": "us",
  "language": "en",
  "max_items": 5,
  "watchMode": false,
  "sort": "most_recent"
}

Caps the run at 5 rows — about $0.0265 on the Free tier ($0.02 start + 5 × $0.0013). country narrows what the source is asked for.

3. Optional watch mode (changes only, for a schedule)

{
  "app_ids": [
    "284882215"
  ],
  "country": "us",
  "language": "en",
  "max_items": 10,
  "watchMode": true,
  "sort": "most_recent"
}

The first run seeds a private baseline and emits zero deltas; every later run emits one row per change, billed at $0.0013 each.

4. Several countries, last 30 days, 1–2 stars only

{
  "app_ids": [
    "284882215"
  ],
  "countries": [
    "us",
    "gb",
    "ca"
  ],
  "recent_days": 30,
  "min_rating": 1,
  "max_rating": 2,
  "max_items": 50,
  "sort": "most_recent"
}

Low-star reviews from the last 30 days across three storefronts — the fastest way to see what is going wrong for users right now.

🧾 JSON sample record

One real record from run 89PPVoRLVT3Feo1UW, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "store": "apple",
  "app_id": "284882215",
  "review_id": "14599347161",
  "title": "I had to give a review",
  "review_text": "I’m starting to believe in you guys",
  "rating": 5,
  "author_handle": "Heisnelson1",
  "review_date": "2026-09-27T05:27:52-07:00",
  "version": "580.0.0",
  "developer_response": null,
  "developer_response_date": null,
  "country": "us",
  "source_url": "https://itunes.apple.com/us/review?id=284882215&type=Purple%20Software",
  "collected_at": "2026-09-28T20:50:32.315869+00:00"
}

🔧 How it works

Source. The actor reads itunes.apple.com — endpoints: https://itunes.apple.com/lookup, https://itunes.apple.com/search. Public pages and feeds only; nothing behind a login.

Transport. Requests go through Apify residential proxy.

Watch semantics. Snapshot mode (watchMode: false) returns a preview. Watch mode keys every record on a source-native id, stores a private baseline in a named key-value store, and on each later run emits one delta row per change (new / changed / removed). A blocked fetch is never diffed, so a source outage cannot show up as a mass removal.

Terminal states. A run ends NORMAL, CAPPED (your cap was reached), PARTIAL (something was withheld and the message says what), GENUINE_EMPTY (the source was read and truly had nothing in scope) or BLOCKED (the source refused or changed shape — the run FAILS loud and bills nothing). A zero-row run is never reported as a silent success.

Charging. Each review scraped is charged at the moment it is pushed (review-scraped); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

🔧 How it works

Transport. Requests go through Apify residential proxy.

🔧 How it works

Transport. Requests go through Apify residential proxy.

🔧 How it works

Transport. Requests go through Apify residential proxy.

🔧 How it works

Transport. Requests go through Apify residential proxy.

How it works

Give it one or more numeric App Store app IDs. It collects the public review-feed entries for each, with bounded retries and a fresh proxy session per attempt, then normalizes every review into one 14-field schema. It reads only public, logged-out surfaces — no login, no paywall, no access-control defeating.

Compliance & honest limits

• Public App Store review surfaces only — no login, CAPTCHA, paywall, or access-control defeating.
• Apple exposes a bounded, recent review window per app; this actor does not reconstruct the full lifetime history.
• A source-confirmed empty result is SUCCEEDED-0: GENUINE_EMPTY; exhausted block retries fail and truncated runs are PARTIAL.

About

Part of the NexGen Watch App Intelligence cluster. Questions or need a custom feed? Open an issue on the Actor page.

Preview vs Watch mode

• Preview (watchMode = false): a one-shot pull of the current reviews — emitted and charged per review-scraped record. Keeps no baseline.
• Watch (watchMode = true): change detection — seeds a private baseline on the first run (zero deltas, no review-scraped billing), then on later runs emits only the new reviews since the baseline, plus one watch-check per run. A settled run with no new reviews reports WATCH_NO_DELTA and charges only the watch-check.

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

⏰ Optional: run it on a schedule

A single run returns the current records. If you also want to be told what changed over time, open the actor in Apify Console → Schedules → Create new, add this actor with the watch-mode input above (watchMode: true) so each run returns only the changes, and pick a cadence:

• Daily — 0 7 * * * (07:00 UTC): catch changes within a day.
• Weekly — 0 7 * * 1: a Monday digest.

Each run is independent; keep the same input on the schedule so the results stay comparable. Schedules can also POST results to a webhook (Console → Integrations).

⏰ Optional: run it on a schedule

⏰ Optional: run it on a schedule

💰 Pricing example

Event	Free	Bronze	Silver	Gold
Actor Start (apify-actor-start)	$0.02	$0.02	$0.02	$0.02
Review scraped (review-scraped)	$0.0013	$0.0012	$0.001	$0.0009
Watch check (watch-check)	$0.10	$0.09	$0.08	$0.067

Worked at the live Free-tier price (watch mode, one delta per change):

• 8 review scrapeds: $0.02 start + 8 × $0.0013 = $0.0304
• 25 review scrapeds: $0.02 start + 25 × $0.0013 = $0.0525
• 100 review scrapeds: $0.02 start + 100 × $0.0013 = $0.15

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 1024 MB.

Yield on the sample run: SUCCEEDED: emitted 25 item(s). max_items is a hard ceiling on what is delivered and billed, never a target.

⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by itunes.apple.com. It collects only what the source publishes to any visitor, identifies itself, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (itunes.apple.com) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input (in watch mode the first run always seeds the baseline and returns zero deltas); BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

Q: How many rows can one run return?
A: Up to max_items (default 100). Raise the cap for a bigger run; you pay per delivered row.

Q: What does watch mode remember between runs?
A: A private baseline of source-native record ids in a named key-value store. Each later run diffs the live source against it and emits only changes.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs except the watch baseline. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other app store intelligence actors?
A: Same output shape and billing model; this one covers itunes.apple.com. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

🆘 Troubleshooting

• Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
• Status says CAPPED → your cap (max_items) was reached → raise it for a bigger run.
• Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
• Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.
• First watch run shows no deltas → expected: it seeds the baseline; changes appear from the second run.

🔗 Related Actors

• App Store & Google Play Metadata Scraper — One Schema — Scrape public Apple App Store and Google Play app metadata by app ID — title, developer, description, category, price, rating, rating count, version,…
• ASO Keyword Rank Scraper - App Store and Google Play — Scrape App Store and Google Play keyword rankings for any app: position per keyword, per country, per store. Every run returns the current records as…
• Google Play Reviews Scraper — Ratings, Text & Replies — Scrape Google Play reviews for any app by package ID or URL: rating, text, thumbs-up, version, date and the developer's reply. Filter by star rating,…
• App Store Top Charts Scraper by Country — Scrape App Store top charts by country and category: rank, app, developer and rank movement. Every run returns the current records as a dataset. Opti…
• 🏢 About NexGen Watch — NexGen Watch is a catalog of more than 300 public data actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.