# App Store Reviews Scraper (`superslowsloth/app-store-reviews-scraper`) Actor

Scrape iOS App Store reviews by app ID or by app name, across any storefront. Returns the review title and body, star rating, author, app version and update time. Pass a name and it is resolved to the right app. Apple's feed exposes up to 500 reviews per app, per storefront, per sort.

- **URL**: https://apify.com/superslowsloth/app-store-reviews-scraper.md
- **Developed by:** [Superslow Sloth](https://apify.com/superslowsloth) (community)
- **Categories:** E-commerce, Automation, AI
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.07 / 1,000 reviews

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## App Store Reviews Scraper

Returns customer reviews for any app on Apple's iOS App Store: rating, title,
review text, author, the app version reviewed, and the date. You can ask for an
app by its numeric App Store id **or just by its name** - names are resolved
through Apple's public search endpoint, and the run log records which app each
name resolved to, so you can check it picked the right one.

### Read this before you pay for a run

**Apple's public review feed is capped at 500 reviews per app, per storefront,
per sort order.** That is 10 pages of 50, and it is Apple's limit, not this
actor's: page 10 returns reviews, page 11 answers HTTP 400. An app with two
million reviews will still return at most 500 of them per storefront. There is
no public Apple endpoint that returns the rest, so no actor - this one or any
other - can give you an app's complete review history from this source.

Two things do increase what you can collect:

- **Run both sort orders.** `mostRecent` and `mostHelpful` each serve their own
  500, and they do not overlap.
- **Run several storefronts.** Reviews are storefront-specific: the `us` feed
  holds only reviews written in the US store, `gb` only British ones, and so
  on. Each storefront is its own 500.

Storefront coverage is uneven and outside anyone's control. Measured on
2026-08-24 for the same app within a few minutes: `us`, `gb`, `fr`, `br`, `in`,
`es`, `it`, `nl`, `se` and `sg` all returned reviews, `de` returned reviews and
then stopped, and `jp` returned an empty feed on more than thirty consecutive
attempts across three different popular apps. When a storefront returns
nothing, the run log says so per app rather than failing the whole run.

### Output

One record per review:

| Field | Notes |
|---|---|
| `id` | Apple's review id. Used for de-duplication across pages. |
| `app_id` | Numeric App Store id the review belongs to. |
| `app_name` | Filled in when the app was requested by name; `null` when you supplied an id, because the feed itself does not carry the app's name. |
| `country` | The storefront the review was read from. |
| `title` | Review headline. |
| `content` | Review body. |
| `rating` | 1-5. |
| `author_name` | Reviewer's display name. |
| `author_url` | Reviewer's iTunes profile URL. |
| `app_version` | The version of the app the reviewer was using. |
| `updated` | ISO timestamp of the review. |
| `vote_count`, `vote_sum` | Helpfulness votes, as Apple reports them. |

Fields Apple's feed does **not** carry, and which this actor therefore never
invents: developer replies, review edit history, reviewer country, and the
app's own metadata beyond what a name lookup returns. Anything missing is
`null`, never `0` or an empty string, because a zero rating or a zero vote
count reads as a measurement rather than an absence.

### Input

| Field | Notes |
|---|---|
| `apps` | Required. Array. Each entry is a numeric id, an `id123456789` string, an App Store URL, or an app name. |
| `country` | Two-letter storefront code, lower case. Default `us`. |
| `maxReviews` | Per app, after de-duplication. Default 100. Values above 500 collect 500. |
| `sortBy` | `mostRecent` or `mostHelpful`. Default `mostRecent`. |
| `proxyConfiguration` | Optional. See below. |

### Reliability

Apple's feed intermittently answers a perfectly good page with an empty
document, then serves the same page in full a moment later. This actor treats
an empty page as a temporary refusal and retries it - with a fresh proxy
address when one is configured - rather than believing it and cutting the run
short. That is also why a proxy is offered even though the feed accepts
datacenter addresses without one: it gives the retry somewhere else to come
from.

Reviews are de-duplicated by Apple's review id **before** anything is charged,
so a page that repeats content never costs you twice.

# Actor input Schema

## `apps` (type: `array`):

One entry per app. Each entry is either a numeric App Store id (310633997), an id string ("id310633997"), an App Store URL, or simply the app's name ("Notion"). Names are resolved through Apple's public search endpoint and the app each name resolved to is written to the run log.

## `country` (type: `string`):

Two-letter App Store storefront code, lower case, for example us, gb, de, fr, br, in. Reviews are storefront-specific: each storefront returns only the reviews written in it, so scraping several countries means several runs. Some storefronts return nothing for some apps - see the README.

## `maxReviews` (type: `integer`):

Upper bound on reviews collected per app, across pages, after duplicates are removed. Apple's public feed serves at most 500 per app per storefront per sort order, so values above 500 collect 500.

## `sortBy` (type: `string`):

mostRecent returns the newest reviews first; mostHelpful returns the ones Apple ranks as most helpful. Both paginate to the same 500-review ceiling, and they return different reviews, so running both roughly doubles what you can collect.

## `proxyConfiguration` (type: `object`):

Optional. Apple's review feed needs no proxy and answers datacenter addresses fine, but it intermittently returns an empty page; a proxy gives the retry a fresh address to try from.

## Actor input object example

```json
{
  "apps": [
    "Notion"
  ],
  "country": "us",
  "maxReviews": 100,
  "sortBy": "mostRecent",
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `reviews` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "apps": [
        "Notion"
    ],
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("superslowsloth/app-store-reviews-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "apps": ["Notion"],
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("superslowsloth/app-store-reviews-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "apps": [
    "Notion"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call superslowsloth/app-store-reviews-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,superslowsloth/app-store-reviews-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/ccvQwrN7jsuekALwn/builds/bchaVYdKPrjepf8s2/openapi.json