App Store Charts Scraper — Top Free, Paid & Grossing | $1/1K | No Key

ASO managers, app publishers, and mobile market analysts use this actor to track weekly chart movements, discover trending apps before they peak, and monitor competitor positions across countries.

$1.00 per 1,000 chart entries. A full 200-app chart costs $0.20. All 3 chart types across 10 countries = $0.60 total.

Worked example:

• Top 100 Free Apps (US) = 100 entries → $0.10
• Full 200-entry chart (any type, any country) → $0.20
• All 3 charts × 10 countries × 200 entries = 6,000 entries → $6.00

200 apps per chart — Apple's RSS supports up to 200 entries, more than any other source.

Top Grossing = revenue intelligence. The Grossing chart is the best proxy for app subscription/IAP revenue — investors and developers use it for competitive due diligence.

Scrape Apple App Store top charts: Top Free, Top Paid, or Top Grossing apps for any country. Uses Apple's open iTunes RSS API — no API key required. Pay per result.

Sample output

{
  "rank": 1,
  "app_id": "544007664",
  "name": "YouTube",
  "developer": "Google LLC",
  "category": "Photo & Video",
  "price": 0.0,
  "chart_type": "free",
  "country": "us",
  "icon_url": "https://is1-ssl.mzstatic.com/...",
  "parse_confidence": 1.0
}

---

What you get

Field	Description
rank	Position in the chart (1 = #1)
app_id	Numeric Apple app ID
bundle_id	Reverse-DNS bundle ID (e.g. com.company.app)
name	App name
developer	Developer/artist name
developer_url	Developer's App Store page
category	Primary category (e.g. Games, Productivity)
category_id	Apple category ID
price	Price in local currency (0.0 for free)
currency	ISO 4217 currency code
url	App Store URL
icon_url	App icon URL (largest available)
summary	Short app description
release_date	Original release date (ISO 8601)
chart_type	"free", "paid", or "grossing"
country	Storefront country code
parse_confidence	Data quality score 0.0–1.0

Usage

{
  "chartType": "free",
  "country": "us",
  "limit": 100
}

Filter by category (Games = 6014):

{
  "chartType": "grossing",
  "country": "gb",
  "limit": 50,
  "genreId": 6014
}

Chart types

Value	Chart
free	Top Free Apps
paid	Top Paid Apps
grossing	Top Grossing Apps

FAQ

Do I need an API key or proxy? No. Apple's iTunes RSS chart feed is fully public — no auth, no proxy, zero setup.

What formats can I export? JSON, CSV, Excel, or JSONL — from the Apify dataset UI or REST API.

Can I schedule it to track weekly chart movements? Yes. Use Apify Scheduler to run weekly per country. Pair with a webhook to Slack or Google Sheets to build a chart-position history automatically.

What if it returns empty results? Apple's RSS occasionally returns an empty feed for certain country/genre combinations. The actor logs a warning and exits cleanly — no data is charged. Try the us storefront first to verify your genreId.

Limits

• Up to 200 apps per chart per country
• Supports all App Store country storefronts (us, gb, de, jp, au, ca, fr, etc.)
• Real-time data directly from Apple's RSS feed

vs. alternatives

Feature	This actor	Sensor Tower	AppFollow	AppMagic
Bulk multi-country charts	✅	✅	✅	✅
Grossing chart (revenue proxy)	✅	✅	✅	✅
Structured JSON output	✅	via API	via API	via API
Pay-per-use (no subscription)	✅	❌	❌	❌
Cost	$1/1K	$99+/mo	$99+/mo	$99+/mo

(Verify competitor prices at publish time — adjust table accordingly.)

parse_confidence — every record carries a 0.0–1.0 data quality score. Score < 0.5 → check the warnings field.

Also see: ASO Keyword Rank Tracker — track keyword-level rankings, not just chart positions.

Use with AI agents (MCP)

All actors in this suite are available via the Apify MCP server. Connect to Claude, GPT-4o, or n8n to let AI agents pull live App Store data on demand — market research, competitor monitoring, and ASO tracking automated end-to-end.

MCP config: https://mcp.apify.com/?tools=bovi/appstore-charts

Also in this suite

• Apple App Store Scraper — full metadata + reviews
• Google Play Store Scraper — Android ecosystem
• App Store Reviews Scraper — reviews-only, bulk NLP use case
• ASO Keyword Rank Tracker — ranking intelligence, 10× cheaper than Sensor Tower
• iOS App Update Tracker — version monitoring

Integrations

Built for ASO managers and mobile market analysts tracking chart positions and top-grossing revenue signals by country — the JSON/dataset output drops into the tools you already run, no glue code:

• n8n / Make / Zapier — trigger a run or pipe every new dataset item into 500+ apps (Google Sheets, Airtable, Slack, HubSpot, your database) with no code: n8n, Make, Zapier.
• Webhooks — fire your own endpoint the moment a run finishes, to push results straight into your pipeline (docs).
• MCP server — expose this actor as a tool to Claude, Cursor, or any MCP client so an AI agent can pull this data mid-conversation (guide).
• API & SDKs — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.

See all Apify integrations.

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Appstore Reviews
• ASO Keyword Tracker
• Google Play Scraper
• Google Search (SERP) Scraper
• Similarweb Traffic Scraper
• App Store Scraper

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.