# Review Scraper API: Datashake Reviews, Ratings and Replies (`nabeelbaghoor/online-review-scraper-api`) Actor

Online reviews API for 100+ review sites: scrape reviews, star ratings, review text, dates, reviewer details and owner replies from any business, product or app review page, plus average rating and review count, through the Datashake Reviews API. Bring your own key.

- **URL**: https://apify.com/nabeelbaghoor/online-review-scraper-api.md
- **Developed by:** [Nabeel Hassan](https://apify.com/nabeelbaghoor) (community)
- **Categories:** Business, Marketing, Developer tools
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 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?

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 Scraper API: Datashake Reviews, Ratings and Replies

Scrape online reviews, star ratings and owner replies from any business, product or app review page on 100+ review sites with your own Datashake key, as clean rows you can export to CSV, Excel or JSON.

Datashake (Reviewshake, Inc.) runs a review data API that collects reviews from review sites, map listings, app stores and marketplaces and returns them in one schema, whatever the site. This actor wraps the Datashake Reviews API: it queues a scrape job for each review page link, waits for it to finish, then fetches every review with its rating, date, text, reviewer details and the business owner's reply, plus the page's review count and average rating. Use it for reputation management, review monitoring, sentiment analysis, competitor benchmarking, local SEO, voice of customer research and BI pipelines. Bring your own API key.

BYOK, not live tested: every route, parameter and response field comes from Datashake's own API documentation (datashake.com/api-docs), and the routes were probed on 2026-11-01 with an invalid key. The actor has not been run against a live Datashake key.

### What it does

- **Scrape reviews**: paste review page links; the actor adds each page to Datashake (one job per page, or the bulk route for several pages), checks progress within a bounded wait, and returns every review of every job that completes.
- **Only new reviews**: collect from a set date, or pass an earlier job ID so Datashake collects only reviews posted since that job.
- **Job reviews**: fetch the reviews of jobs that already exist on your account, with date and language filters, page by page (100 per request).
- **Job and page details**: crawl status, progress, the page's review count and average rating, reviews saved, credits used and business details per job.
- **Job list**: every job on your Datashake account, filtered by creation date and status.
- **One schema for every site**: reviewer name, date, rating, title, text, language, review link, location, verified flag, stable `datashake_review_uuid` for deduplication, and the owner's reply.
- **Pay only for results**: jobs that fail, links Datashake cannot use and jobs still collecting when the wait ends come back as free rows that say why, with the job ID to read later.

### How the asynchronous flow works

Datashake collects reviews in the background, which can take seconds for a small page or hours for a page with thousands of reviews. In Scrape reviews mode the actor:

1. Calls `POST /api/v2/profiles/add` (or `/api/v2/profiles/add_bulk` for several links). This is a documented POST that **creates a scrape job on your own Datashake account and uses its credits**. It is the API's standard read workflow; nothing else on your account is changed.
2. Polls `GET /api/v2/profiles/info` every `pollSeconds` until each job is `complete`, `failed` or `invalid_url`, or until `maxWaitSeconds` runs out.
3. Pages through `GET /api/v2/profiles/reviews` for each completed job.

A job still collecting when the wait ends keeps running on your account. Its job ID is returned in a free row; run the **Job reviews** mode with it later. Datashake requires a callback URL on every job: by default the actor gives the run's own public address, which simply acknowledges the POST. Set `callbackUrl` to your own https endpoint if you also want Datashake to deliver results after the run ends.

### How to get your own key

1. Sign up at dashboard.datashake.com and get your account verified. The free trial includes 20 searches; plans start from $99 a month.
2. Create an API key in the Datashake dashboard.
3. Paste it into the **Datashake API key** field, or set the DATA_API_KEY environment secret.
4. Tick **My Datashake key is on a paid plan**. The Datashake terms forbid non-paying users from caching or storing review data, and this actor stores results in your dataset, so it runs only with a paid plan key.
5. If your verified docs show a different Reviews API base URL, put it in **Base URL**.

### Input

| Field | Modes | Notes |
| --- | --- | --- |
| `mode` | all | `scrapeReviews` (default), `jobReviews`, `jobDetails`, `listJobs` |
| `urls` | scrapeReviews | review page links, one per line, up to 500 |
| `fromDate` | scrapeReviews, jobReviews | only reviews posted on or after, YYYY-MM-DD |
| `diffJobId` | scrapeReviews | earlier job for the same page, one URL only, not with `fromDate` |
| `externalIdentifier` | scrapeReviews | your own ID, sent back with the results |
| `maxWaitSeconds`, `pollSeconds` | scrapeReviews | default 600 and 20 |
| `callbackUrl`, `callbackParameters` | scrapeReviews | your own callback endpoint and its documented headers, query_params, custom_api_key_header, reviews_chunk_size |
| `jobIds` | jobReviews, jobDetails | Datashake job IDs |
| `languageCode` | scrapeReviews, jobReviews | two letter code such as `en` |
| `includeReplies` | scrapeReviews, jobReviews | owner replies, default on |
| `includePageDetails` | scrapeReviews, jobReviews | one page summary row per job, default on |
| `fromCreatedAt`, `crawlStatus` | listJobs | filters |
| `maxResults` | all | most rows returned and charged, default 1,000 |
| `requestsPerMinute` | all | pacing, default 60 |
| `apiKey`, `confirmPaidPlan`, `baseUrl` | all | your key (secret), paid plan confirmation, optional base URL |

### Output

Illustrative review row (shape from Datashake's documented response, values made up, not a live response):

```json
{
    "mode": "scrapeReviews",
    "recordType": "review",
    "found": true,
    "query": "https://www.example-review-site.com/business/northwind-coffee",
    "jobId": "507193846",
    "sourceUrl": "https://www.example-review-site.com/business/northwind-coffee",
    "reviewId": "7302958814",
    "reviewUuid": "4b8e2a17-93c1-3f0d-a6e5-1d7c90b2f364",
    "reviewerName": "Hannah K.",
    "date": "2026-09-14",
    "rating": 5,
    "title": "Best coffee on the harbour",
    "text": "Quick service and the flat white was spot on.",
    "language": "en",
    "location": "Bristol, United Kingdom",
    "verifiedOrder": false,
    "responseName": "Northwind Coffee",
    "responseDate": "2026-09-15",
    "responseText": "Thanks Hannah, see you on Saturday!",
    "pageReviewCount": 214,
    "pageAverageRating": 4.6,
    "note": null,
    "values": { "id": 7302958814, "rating_value": 5, "review_text": "Quick service and the flat white was spot on." }
}
```

Page summary rows (`recordType` `page`) carry `crawlStatus`, `percentageComplete`, `reviewCount`, `averageRating`, `resultCount`, `lastCrawl`, `fromDate`, `uniqueId`, `profileUuid`, `sourceName`, `creditsUsed`, `createdAt` and the parsed `metaData` (business name, address, website, rating breakdown where the site shows them). Job rows (`recordType` `job`) carry `jobId`, `sourceUrl`, `crawlStatus`, `lastCrawl` and `fromDate`. Every row keeps the whole provider record in `values`.

### Pricing

Pay per event, only for rows that carry real Datashake data:

| Event | Price |
| --- | --- |
| Review | $0.005 |
| Review page summary (one per job) | $0.01 |
| Job list record | $0.005 |

Your Datashake plan credits apply on top: each scrape job uses credits on your account. Failed jobs, invalid links, jobs still collecting, empty answers and refused lookups are free. Set `maxResults` to cap a run.

### FAQ

#### What is the Datashake Reviews API?

The Datashake Reviews API (also sold as a Review Scraper API) collects reviews, ratings and owner replies from a business, product or app page on 100+ review sites and returns them in one normalized schema. You add a review page, Datashake creates a job, and you fetch the reviews when the job completes.

#### Does this actor create anything on my Datashake account?

Yes, in Scrape reviews mode only: each review page link becomes one scrape job through the documented `POST /api/v2/profiles/add` route, which is how the Datashake API reads reviews, and it uses your plan's credits. Job reviews, Job and page details and Job list only read jobs that already exist. Schedules and other account settings are never touched.

#### Do I need my own Datashake API key?

Yes. This actor is bring your own key: it sends your key in request headers to the Datashake API and never stores or logs it. Without a key the run ends cleanly with a message saying how to add one.

#### Why must my key be on a paid plan?

Section 4(d) of the Datashake terms of service says non-paying users may not cache or store the data. An Apify dataset is storage, so the actor asks you to confirm the key is on a paid plan before it runs.

#### How long does a scrape take?

From seconds to hours, depending on how many reviews the page holds. The actor waits up to `maxWaitSeconds` (default 10 minutes, up to 50). Anything not finished is returned with its job ID, free, to read later with Job reviews.

#### Can I collect only new reviews?

Yes. Set `fromDate` to collect reviews posted on or after a date, or set `diffJobId` to an earlier job for the same page and Datashake collects only reviews posted since then. Use `reviewUuid` (Datashake's stable review ID) to remove duplicates across jobs.

#### Which review sites are supported?

Datashake covers 100+ review sites; the full source list is in your Datashake docs once your account is verified. If a link is refused, check that it is the main review page of the business or product, not a single review.

#### What do I pay?

$0.005 per review, $0.01 per page summary and $0.005 per listed job, plus your own Datashake plan. Failed, invalid, pending and empty results are free.

### Keyword map

review scraper API, online reviews API, review data API, Datashake API, Reviewshake API, scrape reviews, review aggregation API, star ratings API, business reviews data, product reviews scraper, app store reviews API, owner replies, reputation management data, review monitoring, sentiment analysis data, local SEO reviews, voice of customer data.

### Routes and verification

| Mode | Route | Probe with invalid key (twice) |
| --- | --- | --- |
| Scrape reviews (add) | POST /api/v2/profiles/add, POST /api/v2/profiles/add_bulk | not probed (would queue a job) |
| Scrape reviews (wait), Job and page details | GET /api/v2/profiles/info | 401 {"success":false,"message":"Invalid API key provided","status":401} |
| Scrape reviews (fetch), Job reviews | GET /api/v2/profiles/reviews | 401 |
| Job list | GET /api/v2/profiles/jobs | 401 |
| Invented control routes | GET /api/v2/profilez/foo, GET /api/v2/profiles/fetch_all | 404 {"detail":"Not Found"} |

The default host is `https://app.datashake.com`. Datashake's current docs name the key header `x-api-key`; the live host answered a key sent only that way with "missing API token" and read the `spiderman-token` header of Datashake's earlier docs instead, so every request sends the key in both headers, never in a URL or a log line. The Location Search, Social Media, E-commerce and Scheduling APIs are not wrapped.

### Licensing and data use

This actor works only with your own Datashake key, and your agreement with Datashake applies. The Datashake terms of service (section 4) limit use of the service to your internal business purposes, bar reselling or redistributing the data or making the service available to third parties, and forbid non-paying users from caching or storing the data. Use a paid plan key and keep the results for your own internal analysis. The reviews themselves are content posted on third party sites; respect those sites' terms and reviewers' privacy. This actor is not affiliated with or endorsed by Datashake or Reviewshake, Inc.

# Actor input Schema

## `mode` (type: `string`):

Scrape reviews queues one Datashake job per review page link, waits for it within the maximum wait and returns every review. Job reviews and Job and page details read jobs that already exist on your account; Job list lists your jobs.

## `urls` (type: `array`):

Scrape reviews. One review page link per line: the main page of a business, product or app on a review site Datashake supports (not a single review). Each link becomes one job on your Datashake account and uses its credits. Up to 500 per run.

## `fromDate` (type: `string`):

Scrape reviews and Job reviews. Only collect, and only return, reviews posted on or after this date (YYYY-MM-DD).

## `diffJobId` (type: `string`):

Scrape reviews, with exactly one URL. The ID of an earlier job for the same page: Datashake then collects only reviews posted since that job. Cannot be combined with the from date.

## `externalIdentifier` (type: `string`):

Scrape reviews. Your own ID for the job (up to 255 characters), sent back with the results so they match your records.

## `maxWaitSeconds` (type: `integer`):

Scrape reviews. How long to wait for the jobs to finish. Pages with thousands of reviews can take longer; any job still collecting is returned with its job ID, free, to read later with Job reviews.

## `pollSeconds` (type: `integer`):

Scrape reviews. How often to check each job's progress while waiting.

## `callbackUrl` (type: `string`):

Scrape reviews. Datashake requires a callback URL for every job and POSTs the results there when the job ends. Leave empty to use this run's own address, which only acknowledges it; set your own public https endpoint to also receive results after the run ends.

## `callbackParameters` (type: `object`):

Scrape reviews, with your own callback URL. The documented callback_parameters object: headers, query_params, custom_api_key_header and reviews_chunk_size.

## `jobIds` (type: `array`):

Job reviews and Job and page details. One Datashake job ID per line, from a Scrape reviews run, the Job list mode or your own integration.

## `languageCode` (type: `string`):

Scrape reviews and Job reviews. Only return reviews in this language, as a two letter code such as en. Support varies by site.

## `includeReplies` (type: `boolean`):

Scrape reviews and Job reviews. Return the business owner's reply with each review, where there is one.

## `includePageDetails` (type: `boolean`):

Scrape reviews and Job reviews. Add one row per job with the page's review count, average rating, crawl status and business details.

## `fromCreatedAt` (type: `string`):

Job list. Only list jobs created on or after this date (YYYY-MM-DD).

## `crawlStatus` (type: `string`):

Job list. Only list jobs with this status.

## `maxResults` (type: `integer`):

The most rows this run returns and charges for.

## `requestsPerMinute` (type: `integer`):

Pacing of calls to the Datashake API. Lower it if your plan's rate limit answers 429.

## `apiKey` (type: `string`):

Your own Datashake API key, created in the Datashake dashboard once your account is verified. Stored encrypted. Or set the DATA_API_KEY environment secret.

## `confirmPaidPlan` (type: `boolean`):

Required. The Datashake terms of service forbid non-paying users from caching or storing review data, and this actor stores results in your dataset. Tick this to confirm the key belongs to a paid Datashake plan.

## `baseUrl` (type: `string`):

The Reviews API base URL from your verified Datashake docs, if it differs from the default https://app.datashake.com. Only https addresses on datashake.com are accepted.

## Actor input object example

```json
{
  "mode": "scrapeReviews",
  "maxWaitSeconds": 600,
  "pollSeconds": 20,
  "includeReplies": true,
  "includePageDetails": true,
  "crawlStatus": "",
  "maxResults": 1000,
  "requestsPerMinute": 60,
  "confirmPaidPlan": false
}
```

# Actor output Schema

## `records` (type: `string`):

One row per review, page summary or job the chosen mode read.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("nabeelbaghoor/online-review-scraper-api").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("nabeelbaghoor/online-review-scraper-api").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 '{}' |
apify call nabeelbaghoor/online-review-scraper-api --silent --output-dataset

```

## MCP server setup

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

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/WrZJkynee3AGJiT6M/builds/6PgEpkYJvbh9RAF4y/openapi.json
