Apple App Store Reviews Scraper
Pricing
from $1.60 / 1,000 standard calls
Apple App Store Reviews Scraper
Export App Store customer reviews for any app and storefront: rating, title, body, author, version and date, sorted by most recent or most helpful. Paginated for bulk export into sentiment analysis.
Pricing
from $1.60 / 1,000 standard calls
Rating
0.0
(0)
Developer
ScrapeBadger
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
5 days ago
Last modified
Categories
Share
What does Apple App Store Reviews Scraper do?
Apple App Store Reviews Scraper extracts structured data from the App Store and delivers it as clean JSON — no proxies, browsers or anti-bot handling on your side. It is a practical the App Store API alternative for teams who need the App Store data on a schedule rather than a one-off export.
It covers 1 different the App Store surface behind a single Mode dropdown, so one Actor replaces a rack of single-purpose scrapers.
Why scrape the App Store?
- Every surface in one place — pick a mode, fill two fields, run.
- Anti-bot handled upstream — residential proxy rotation, TLS and browser fingerprinting, and CAPTCHA solving happen inside the ScrapeBadger API.
- Pay per call, not per row — a page of results costs the same as one lookup, so bulk work stays cheap.
- Runs on the Apify platform — scheduling, monitoring, webhooks, the API, and integrations with Make, Zapier, Google Sheets, Slack and Airtable all work out of the box.
- Partial results are kept — a transient upstream failure ends the run cleanly instead of discarding what you already paid for.
What data can Apple App Store Reviews Scraper extract?
Every record is pushed to the dataset as its own row. The most useful fields are below; the full record carries considerably more.
| Field | Type | Description |
|---|---|---|
rating | number | Average rating |
title | string | Title of the record |
body | string | Full text body of the review |
author | string | Display name of the author |
version | string | App version the review was left on |
date | string (ISO 8601) | Publication date |
the App Store scraping modes
Pick one Mode; the input form marks the fields it needs.
| Mode | What it returns | Charged as |
|---|---|---|
| Get App Reviews | Reviews with rating, title, body, author, version and date. | standard-call |
How to scrape the App Store
- Click Try for free and sign in to Apify.
- Open Settings → Environment variables and add
SCRAPEBADGER_API_KEYwith your key from scrapebadger.com, ticking Secret. - Choose a Mode from the dropdown.
- Fill in the fields that mode needs — the description on each field says which modes use it.
- Set Max items to cap the run.
- Press Start and watch the dataset fill up.
- Export as JSON, CSV, Excel or XML, or pull it from the API tab.
How much will it cost to scrape the App Store?
This Actor is pay per event: one event per API call, whatever that call returns. Fetching a page of 100 records costs the same as fetching one record, so larger pages are cheaper per row.
| Event | Price per event | What triggers it |
|---|---|---|
standard-call | $0.0020 | A standard call — one search page, profile, or detail record. |
Apify also charges its standard $0.001 actor start fee per run. ScrapeBadger credits are consumed on your own account on top of this.
Input
See the Input tab for every option with inline documentation. A minimal run looks like this:
Max items caps the run; the Actor pages until it reaches that number or the App Store runs out of results.
Output
You can download the dataset in various formats such as JSON, HTML, CSV, or Excel, or read it straight from the Apify API. Each record is one row:
What can you do with the App Store data?
A few things teams actually build with this Actor.
Mine competitor reviews for your roadmap
One-star reviews on a rival app are a list of problems your product could solve. Exporting and clustering them is the single highest-return research task in app product management.
Track sentiment across releases
Reviews carry the app version. Grouping sentiment by version shows exactly which release broke something.
Monitor reviews across storefronts
Sentiment often differs sharply by country. Pulling several storefronts catches localisation problems that a US-only view hides completely.
Feed reviews into support and QA
Routing new negative reviews into your issue tracker automatically closes the loop between the store and engineering.
Tips for faster, cheaper runs
- Raise the page-size field (
count,limit,per_page— whichever the mode exposes) before raising Max items. Fewer, bigger calls cost less. - Use the cheap reference and autocomplete modes to resolve IDs before spending on the expensive detail modes.
- Schedule incremental runs with a low Max items rather than one huge sweep; you get fresher data and a smaller bill.
- Chain Actors with webhooks to push new rows straight into your warehouse.
Requirements
This Actor calls the ScrapeBadger API on your behalf, so it needs your key:
- Get one at scrapebadger.com — there is a free tier.
- In Settings → Environment variables, add
SCRAPEBADGER_API_KEYwith yoursb_live_…key and tick Secret.
Credits are consumed on your ScrapeBadger account in addition to the Apify event price.
Frequently asked questions
Is it legal to scrape the App Store?
Scraping publicly available data from the App Store is generally legal, and this Actor only ever reads pages a logged-out visitor could see. What you then do with the data is what matters — read the disclaimer below before collecting anything that could be personal data.
Do I need my own proxies?
No. Proxy rotation, browser fingerprinting and anti-bot handling all happen upstream in the ScrapeBadger API, so there is nothing to configure here.
Do I need a ScrapeBadger account?
Yes. The Actor calls the ScrapeBadger API on your behalf, so it needs your API key in the SCRAPEBADGER_API_KEY environment variable. There is a free tier at scrapebadger.com — see Requirements below.
How many results can I get in one run?
Set Max items to whatever you need. The Actor keeps paging until it hits that number or the App Store runs out of results, and stops cleanly either way.
How much does one run cost?
Events start at $0.0020 and are charged once per API call, not per row — so a page of 100 results costs the same as a single lookup. Apify adds its standard $0.001 actor start fee per run.
What happens if the run fails halfway through?
Whatever was already scraped stays in the dataset. The run ends with a status message explaining where it stopped instead of throwing your results away.
Can I run this on a schedule or from my own code?
Yes. Use the Schedules tab for recurring runs, or the API tab to start runs and read the dataset from your own application.
Is scraping the App Store reliable?
Anti-bot interstitials are a fact of life on the App Store. A blocked call is retried four times with exponential backoff against fresh exits, and if a run dies partway it keeps everything already scraped rather than throwing the dataset away. Upstream availability is monitored continuously.
Your feedback and support
Found a bug, missing a field, or need a mode that is not here? Open a ticket on the Issues tab, or email support@scrapebadger.com. The API tab has everything you need to run this Actor programmatically.
Disclaimer
Our Actors are ethical and do not extract any private user data, such as email addresses, gender, or location. They only extract what the user has chosen to share publicly. We therefore believe that our Actors, when used for ethical purposes by Apify users, are safe. However, you should be aware that your results could contain personal data. Personal data is protected by the GDPR in the European Union and by other regulations around the world. You should not scrape personal data unless you have a legitimate reason to do so. If you're unsure whether your reason is legitimate, consult your lawyers.
