Apple App Store Scraper — Search, Apps & Charts

What does Apple App Store Scraper do?

Apple App Store 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 6 different the App Store surfaces 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 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
app_id	string	App id
name	string	Name of the record
developer_name	string	Publisher of the app
rating	number	Average rating
price	number	Price as a number
url	string (URL)	Canonical URL of the record

the App Store scraping modes

Pick one Mode; the input form marks the fields it needs.

Mode	What it returns	Charged as
Search Apps	Apps matching a keyword in one storefront.	standard-call
Get App Detail	Full app record: ratings, size, screenshots, release notes, genres.	standard-call
Top Charts	Top free, paid or grossing apps, optionally within one genre.	standard-call
Get Developer Apps	Everything a developer has published.	standard-call
List Genres	Genre IDs for the charts filter.	basic-call
List Markets	Supported storefront country codes.	basic-call

How to scrape the App Store

1. Click Try for free and sign in to Apify.
2. Open Settings → Environment variables and add SCRAPEBADGER_API_KEY with your key from scrapebadger.com, ticking Secret.
3. Choose a Mode from the dropdown.
4. Fill in the fields that mode needs — the description on each field says which modes use it.
5. Set Max items to cap the run.
6. Press Start and watch the dataset fill up.
7. 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
basic-call	$0.0010	A cheap call — autocomplete, reference data, single lookups.
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:

{
  "mode": "Search Apps",
  "query": "notion",
  "app_id": "1232780281",
  "country": "us",
  "max_items": 100
}

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:

{
  "app_id": "<app_id>",
  "name": "<name>",
  "developer_name": "<developer_name>",
  "rating": 1234,
  "price": 1234,
  "url": "https://example.com/record/1"
}

What can you do with the App Store data?

A few things teams actually build with this Actor.

Run App Store Optimisation research

Search a keyword across storefronts and see who ranks. Because ASO rankings differ sharply by country, the per-storefront view is where the opportunity usually is.

Track competitor releases

Version numbers and release notes on a schedule tell you what competitors ship and how often. Release notes are the cheapest product-roadmap intelligence available.

Analyse chart movement

Top free, paid and grossing by genre and country, sampled daily, shows which apps are climbing — usually the ones that just started spending.

Map a developer's portfolio

A developer's full catalogue reveals whether a competitor is one product or a portfolio, and where their revenue actually concentrates.

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:

1. Get one at scrapebadger.com — there is a free tier.
2. In Settings → Environment variables, add SCRAPEBADGER_API_KEY with your sb_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.0010 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.

Notes on the App Store

The App Store search surface is rate-sensitive: hammering it with undocumented parameters gets a storefront banned for a while. The upstream API keeps the request shape conservative, so stick to the fields exposed here.