# Review Aggregator - Trustpilot and App Store in One Schema (`alaudinburki/review-aggregator`) Actor

Every review for a business or app in one schema, newest first: rating, text, author, date, and whether the owner replied, across Trustpilot and the Apple App Store.

- **URL**: https://apify.com/alaudinburki/review-aggregator.md
- **Developed by:** [alaudin burki](https://apify.com/alaudinburki) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 results

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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Review Aggregator — Trustpilot and App Store in One Schema

Every review for a business or app in **one schema, newest first** — rating, text, author, date, and
whether the owner replied — across **Trustpilot** and the **Apple App Store**.

The merge is the product. A business's reputation is split across a review site and the app stores,
and **every incumbent covers exactly one platform**: the biggest Trustpilot actor returns Trustpilot
only, the biggest app-store actor returns app stores only. Nobody returns both.

### What you get

**Default dataset — one row per review**

| Field | Description |
|---|---|
| `id` | `trustpilot:<domain>:<id>` or `apple:<appId>:<id>` |
| `platform` | `trustpilot` or `apple` |
| `subject` | The domain or app |
| `rating` | 1–5 |
| `title`, `body`, `author` | As published |
| `publishedAt` | ISO timestamp |
| `ownerReplied` | `true` / `false` on Trustpilot; **`null` on Apple**, which carries no reply field |
| `version` | iOS version, Apple only |
| `url`, `scrapedAt` | Link and read time |

**Dataset `reputation` — one row per subject**

`reviews`, `negative`, `positive`, `averageRating`, `ownerReplied`, `answerableReviews`,
**`unanswered`**, and **`unansweredNegative`** — the count of one-and-two-star reviews nobody answered.

### Sample output

```
apple:WhatsApp Messenger — 100 reviews
trustpilot:www.amazon.com — 15 reviews, 0 replied
75 reviews across 2 subject(s); 0 problem(s)
```

### Default input

Runs with no editing: `www.amazon.com` on Trustpilot and `WhatsApp Messenger` on the App Store.

### Limitations — read before buying

- **Trustpilot needs a browser**, so this Actor runs on the Playwright image and is slower than a
  plain-HTTP scraper. That is unavoidable: a plain request returns **HTTP 403** and the review cards
  only exist after JavaScript runs.
- **Apple's public feed carries no developer reply**, so `ownerReplied` is `null` there and Apple
  reviews are **excluded from `unanswered`** rather than being counted as ignored customers. The
  summary reports `answerableReviews` so you can see the denominator.
- **Not included:** Google Maps and Google Play are JavaScript applications whose reviews come from
  signed internal calls; **Yelp** returns 403 even to a browser session, **Facebook Pages** and the
  **Meta Ad Library** return 403. They are absent, not approximated.
- **`unansweredNegative` is a reply signal, not satisfaction.** A business may answer every review
  politely and still be terrible.
- One review per card; Trustpilot shows a page at a time, so deep history needs repeated runs.

### Pricing

Pay per result.

# Actor input Schema

## `trustpilotDomains` (type: `array`):

Trustpilot review pages to read, given as the domain in the URL. e.g. www.amazon.com for trustpilot.com/review/www.amazon.com. Read with a headless browser.

## `appStoreApps` (type: `array`):

Apple App Store apps by name or numeric id. Read from the public reviews feed.

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

Two-letter storefront for App Store reviews.

## `appleReviewPages` (type: `integer`):

50 reviews per page, newest first.

## `maxReviewsPerSubject` (type: `integer`):

Cap per business or app.

## `includeSummary` (type: `boolean`):

Write a second dataset with one row per subject: averages, negatives and unanswered counts.

## `maxItems` (type: `integer`):

Stop after this many review rows.

## Actor input object example

```json
{
  "trustpilotDomains": [
    "www.amazon.com"
  ],
  "appStoreApps": [
    "WhatsApp Messenger"
  ],
  "country": "us",
  "appleReviewPages": 3,
  "maxReviewsPerSubject": 200,
  "includeSummary": true,
  "maxItems": 5000
}
```

# Actor output Schema

## `results` (type: `string`):

One row per item, with the 7 fields listed under Views.

# 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 = {
    "trustpilotDomains": [
        "www.amazon.com"
    ],
    "appStoreApps": [
        "WhatsApp Messenger"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("alaudinburki/review-aggregator").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 = {
    "trustpilotDomains": ["www.amazon.com"],
    "appStoreApps": ["WhatsApp Messenger"],
}

# Run the Actor and wait for it to finish
run = client.actor("alaudinburki/review-aggregator").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 '{
  "trustpilotDomains": [
    "www.amazon.com"
  ],
  "appStoreApps": [
    "WhatsApp Messenger"
  ]
}' |
apify call alaudinburki/review-aggregator --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,alaudinburki/review-aggregator"
        }
    }
}
```

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/xiUja48ptBv7XCQip/builds/ws6dzF6JHevrQF8nK/openapi.json