# Capterra Reviews Scraper: Pros, Cons, Company Size (`arcadium/capterra-reviews`) Actor

Capterra reviews for product URLs: rating, pros, cons, text, reviewer role, industry and company size, incentivized flag; $1.79 per 1,000 reviews. Capterra sorts and filters server-side, up to 50,000 per product. Native review IDs, only-new mode, no reviewer names, free error rows.

- **URL**: https://apify.com/arcadium/capterra-reviews.md
- **Developed by:** [Arcadium Data](https://apify.com/arcadium) (community)
- **Categories:** Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.16 / 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.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## Capterra Reviews Scraper: Pros, Cons, Company Size

Give it Capterra product URLs and it returns one JSON row per review: overall and sub-ratings, pros, cons, review text, the reviewer's role, industry and company size, how long they used the product and the incentivized flag. $1.79 per 1,000 reviews on the free plan, and you pay only for the rows you get.

**Why this actor**

- Capterra's own sort and filters (stars, company size, role, usage) run server-side, so the rows are exactly the slice you asked for.
- Up to 50,000 reviews per product, past the 2,500 you reach by clicking through the site.
- Native review IDs for deduplication, and `onlyNewReviews` for weekly monitoring.
- Input names of other Capterra review scrapers (`productUrl`, `maxResults`, `sort`, `starRating`) work as they are. Free error rows with a machine-readable `code` (`not_found`, `blocked`, `unavailable`...), so an agent knows whether to retry.

Built by Arcadium Data: public data, dated and agent-ready, never personal data.

### Use with AI agents

Returns Capterra reviews (pros, cons, rating, reviewer role and company size) for software product URLs. Agents can call it through the Apify MCP server (`https://mcp.apify.com`, open source as `apify/actors-mcp-server`) as `arcadium/capterra-reviews`: the input schema is read from the actor, the result is a dataset of JSON rows.

Input example (minimal):

```json
{
  "startUrls": [
    {
      "url": "https://www.capterra.com/p/135003/Slack/reviews/"
    }
  ],
  "maxReviewsPerProduct": 20
}
```

What comes back: one `review` row per review (charged), free `coverage` rows (stated total vs delivered) and a free `error` row for an input that could not be read. Filter on the `rowType` field. An input that fails is reported, not hidden (`includeErrorRows`, on by default): the error row carries `rowType: "error"`, a `code` (`invalid_input`, `not_found`, `blocked`, `unavailable`, `filter_unsupported` or `no_match`), a `message` and the `input` it is about. Retry on `blocked` and `unavailable` later; do not retry the other codes with the same input.

Cost of the call above: 20 reviews at $1.79 per 1,000 plus the $0.001 start fee is about $0.04 on the free plan; paid plans pay less. Free rows are never charged.

### What you get per review

Output example:

```json
{
  "rowType": "review",
  "platform": "capterra",
  "productName": "Slack",
  "productUrl": "https://www.capterra.com/p/135003/Slack/",
  "entityId": "135003",
  "reviewId": "Capterra___7224147",
  "reviewUrl": "https://www.capterra.com/p/135003/Slack/#Capterra___7224147",
  "title": "Very strong communication tool.",
  "text": "Generally very good, quick and easy. Good options to integrate, easy to file share. I typically run multiple Slack instances.",
  "pros": "Ability to communicate in real time with colleagues when we're working remotely. Also for file sharing.",
  "cons": "The threads feature is not something that I find particularly intuitive...",
  "ratingOverall": 5,
  "ratings": { "easeOfUse": 5, "customerService": 4, "features": 5, "valueForMoney": 5, "likelihoodToRecommend": 9 },
  "date": "2026-10-02",
  "reviewerRole": "CPO",
  "reviewerIndustry": "Computer Software",
  "reviewerCompanySize": "1-10 employees",
  "reviewerTimeUsed": "1-2 years",
  "switchedFrom": "Google Workspace",
  "reasonForSwitching": "Google Workspace chat works well. However, several of our technical staff wanted to use Slack.",
  "incentivized": true,
  "incentive": "NominalGift",
  "reviewerVerified": true,
  "product": {
    "platform": "capterra",
    "entityId": "135003",
    "name": "Slack",
    "url": "https://www.capterra.com/p/135003/Slack/",
    "rating": 4.7,
    "reviewCount": 24229,
    "category": "Team Communication",
    "vendor": "Slack",
    "website": null
  },
  "scrapedAt": "2026-10-20T17:49:58.237Z"
}
```

A few fields worth knowing about:

`reviewId` is Capterra's own ID, so it stays the same between runs. Use it to dedupe when you scrape the same product every week.

`incentivized` tells you whether Capterra marked the review as written for a gift card or similar reward. Plenty are. If you're doing sentiment analysis you probably want to look at both groups separately.

`switchedFrom`, `alternativesConsidered` and `reasonForSwitching` are filled only when the reviewer answered those questions, which is maybe one review in four. They're the most useful fields for competitive research, so the gaps are a pity, but that's the data.

`product` repeats on every review, so each row stands on its own when you load it into a spreadsheet or a database. The same product, plus pricing plans, alternatives, features and integrations, is saved once per product in the `PRODUCT` record of the run's key-value store.

Sub-ratings are left out when the reviewer skipped them (you won't see a fake 0). `likelihoodToRecommend` is on a 0 to 10 scale; the rest are 1 to 5.

Reviewer names and profile photos are never collected. You get the role and company details, not the person.

### Input

Give it `startUrls`. Any Capterra product link works, with or without `/reviews/` at the end, and the regional Capterra sites (capterra.co.uk, capterra.com.au and so on) are accepted too:

```json
{
  "startUrls": [
    { "url": "https://www.capterra.com/p/135003/Slack/" },
    { "url": "https://www.capterra.com/p/186596/Notion/reviews/" }
  ],
  "maxReviewsPerProduct": 500,
  "sort": "MOST_RECENT"
}
```

If you call the actor through the API, note the `{ "url": ... }` objects. A plain list of strings gets rejected by Apify's input validation.

Everything else is optional:

| Field | What it does |
| --- | --- |
| `maxReviewsPerProduct` | How many reviews to collect per product. Default 100, max 50,000. |
| `sort` | Most recent, most helpful, highest rated or lowest rated. Same options as the site. |
| `minRating`, `maxRating` | Overall star range, for example 1 to 2 if you only want complaints. |
| `dateFrom` | Only reviews from this date on (YYYY-MM-DD). With "Most recent" the run stops as soon as it reaches older reviews, so you don't pay for anything you'll throw away. |
| `companySizes` | Self-employed, 1-10, 11-50 and so on up to 10,001+ employees. |
| `reviewerRoles` | User, administrator or other. |
| `timeUsed` | Free trial, under 6 months, 6-12 months, 1-2 years, 2+ years. |
| `usageFrequency` | Daily, weekly, monthly, other. |
| `includeProductDetails` | On by default. Adds the product's exact name, rating, category and vendor to every review and saves the full profile (pricing, alternatives, features, integrations) in `PRODUCT`. Turn it off if you only care about the reviews; the name is then taken from the URL. |
| `onlyNewReviews`, `stateKey` | Incremental mode for scheduled runs. Only reviews that earlier runs with the same `stateKey` did not deliver are returned, and only those are charged. Uses the "Most recent" sort. The state lives in a key-value store named `capterra-reviews-seen` in your account; pick a new `stateKey` to start from scratch. |
| `includeErrorRows` | On by default. An input that can't be scraped (bad URL, product not found) produces one row with `"rowType": "error"` and a `code`, and the run still succeeds. Error rows are never charged. |
| `includeCoverageRows` | On by default. One free row per product with `"rowType": "coverage"`: the review total the site states, how many were delivered, why the run stopped and whether anything is missing (`shortfall`). Never charged. |
| `markEdited` | On by default, with `onlyNewReviews`. Reviews seen before whose text changed in the last 7 days are delivered again with `extras.changeType` set to `edited` (charged like a new review). New ones carry `new`. |

Filters are applied by Capterra before anything is downloaded. Ask for 1-star reviews from companies with 1-10 employees and you'll get exactly those, without paging through thousands of others first.

### How many reviews can I get?

All of them, up to 50,000 per product. There's no 2,500 cap like the one you hit when clicking through pages on the site. In our tests Slack reviews came through all the way back to 2017. Most products have far fewer reviews, so this mostly matters for the big names.

A run of 1,000 reviews usually takes under a minute.

### Coming from zen-studio's Capterra scraper?

These input names work as they are: `productUrl` (one link), `maxResults` (0 means no limit), `sort` (including `HIGHEST_COMPLETENESS_SCORE`, which becomes "most helpful") and `starRating` (a list such as `["1","2"]`, applied as a min to max range). `feedback` is ignored. The first time one of these names is used, the run log says which of our fields it was mapped to.

### Pricing

You pay per review delivered, at the price of your Apify plan. Coverage rows, error rows and repeats in only-new mode are free.

| Apify plan | Per 1,000 reviews |
| --- | --- |
| Free | $1.79 |
| Starter (Bronze) | $1.34 |
| Scale (Silver) | $1.25 |
| Business (Gold) | $1.16 |
| Platinum | $1.16 |
| Diamond | $1.16 |

Plus a one-off $0.001 per GB of memory when a run starts.

Set a maximum cost per run in the Apify run options and the actor stops before it goes over.

### Related actors and data

- [Software Reviews Scraper: Capterra, Google Play, App Store](https://apify.com/arcadium/software-reviews)
- [Capterra Products Scraper: Pricing, Features, Rank](https://apify.com/arcadium/capterra-products)
- [TrustRadius Reviews Scraper: Pros, Cons, Reviewer Role](https://apify.com/arcadium/trustradius-reviews)
- [Review Monitor: Negative Review Alerts and Rating Drift](https://apify.com/arcadium/reputation-monitor)
- [Arcadium Data MCP Server](https://apify.com/arcadium/arcadium-mcp): AI agents can ask the same questions as tools (`search_reviews`, `review_snapshot`).

### Limitations

Capterra doesn't publish a stable public API, so the site can change without warning. We run checks against the live site every day and usually notice breakage before you do. If Capterra changes something big, the actor keeps working in a reduced mode (default order, up to 2,500 reviews per product) while we fix it. In that mode the reviewer role and usage frequency filters can't be applied, so a product that uses them fails with a clear message instead of returning the wrong reviews.

`helpfulVotes` and `language` are part of our shared review format but Capterra doesn't expose them, so they're always empty here. `reviewUrl` is the product URL plus the review ID as an anchor; Capterra has no page of its own for a single review.

The vendor website isn't published in the data we read, so `product.website` is empty. Reviews from the regional Capterra sites are read from capterra.com, which lists the same products and reviews.

In the reduced mode described above, `onlyNewReviews` can't rely on newest-first order and may miss new reviews that sit deeper than the first pages. It goes back to normal as soon as the standard mode works again.

Vendor replies (`vendorResponse`) are rare on Capterra. We haven't seen one in our test data yet, so treat that field as best effort.

### Is this allowed?

The actor only reads reviews that anyone can see on Capterra without logging in, and it doesn't collect personal data about reviewers. How you use the data is up to you. If you plan to republish review text, check Capterra's terms first.

### Questions or problems

Open an issue on the Issues tab with the product URL and your input. If something's broken we'd rather hear about it than have you quietly give up on the actor.

# Actor input Schema

## `startUrls` (type: `array`):

Capterra product or reviews page URLs, e.g. https://www.capterra.com/p/135003/Slack/reviews/. Regional Capterra sites (capterra.co.uk, capterra.com.au, ...) are accepted and read from capterra.com. Leave empty if you use search queries.

## `maxReviewsPerProduct` (type: `integer`):

Maximum number of reviews to collect for each product (up to 50,000). Default: 100.

## `sort` (type: `string`):

Order in which reviews are listed. Applied by Capterra (server-side).

## `minRating` (type: `integer`):

Only keep reviews with an overall rating of at least this value (1-5). Applied by Capterra (server-side).

## `maxRating` (type: `integer`):

Only keep reviews with an overall rating of at most this value (1-5). Applied by Capterra (server-side).

## `dateFrom` (type: `string`):

Only keep reviews published on or after this date (YYYY-MM-DD, or a relative span such as 30 days or 2 months; empty = no filter). With 'Most recent' sorting, paging stops once reviews are older.

## `companySizes` (type: `array`):

Only reviews from reviewers at companies of these sizes (applied by Capterra).

## `reviewerRoles` (type: `array`):

Only reviews from these kinds of reviewers (applied by Capterra).

## `timeUsed` (type: `array`):

Only reviews from reviewers who used the product for this long (applied by Capterra).

## `usageFrequency` (type: `array`):

Only reviews from reviewers who use the product this often (applied by Capterra).

## `includeProductDetails` (type: `boolean`):

Add the product name, rating, category, vendor, pricing and alternatives to every review and to the PRODUCT record. When off, the product name is derived from the URL and the product fields stay empty.

## `onlyNewReviews` (type: `boolean`):

Return only reviews not delivered by earlier runs that used the same state key. Uses the 'Most recent' sort order. The state is kept in a named key-value store in your account (change the state key to start over). Skipped reviews are not charged.

## `stateKey` (type: `string`):

Name of the incremental state used by 'Only new reviews' (letters, digits and dashes, up to 40 characters). Use different keys for independent schedules. Example: weekly-monitoring.

## `includeErrorRows` (type: `boolean`):

Add one row with rowType 'error' (not charged) for each input that could not be scraped, e.g. a product that does not exist.

## `includeCoverageRows` (type: `boolean`):

Add one free row with rowType 'coverage' per product or source: the review total the site states, how many were delivered, why paging ended and whether anything is missing. Not charged.

## `markEdited` (type: `boolean`):

With 'Only new reviews': also deliver reviews seen before whose text changed in the last 7 days, marked extras.changeType 'edited'. Edited reviews are charged like new ones.

## `maxRetries` (type: `integer`):

How many times a failed page request is retried before the product is skipped.

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

Optional. By default the actor automatically picks the cheapest working proxy. Set this only to force your own proxy setup.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://www.capterra.com/p/135003/Slack/reviews/"
    }
  ],
  "maxReviewsPerProduct": 20,
  "sort": "MOST_RECENT",
  "includeProductDetails": true,
  "onlyNewReviews": false,
  "stateKey": "default",
  "includeErrorRows": true,
  "includeCoverageRows": true,
  "markEdited": true,
  "maxRetries": 3
}
```

# Actor output Schema

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

All rows of this run in the default dataset.

## `view_overview` (type: `string`):

No description

## `view_ratings` (type: `string`):

No description

## `view_errors` (type: `string`):

No description

## `view_coverage` (type: `string`):

No description

## `record_stats` (type: `string`):

Requests, data volume, retries, cost per result and per-product summaries for this run.

## `record_product` (type: `string`):

One profile per scraped product: category, vendor, pricing, alternatives, features and integrations.

# 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 = {
    "startUrls": [
        {
            "url": "https://www.capterra.com/p/135003/Slack/reviews/"
        }
    ],
    "maxReviewsPerProduct": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("arcadium/capterra-reviews").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 = {
    "startUrls": [{ "url": "https://www.capterra.com/p/135003/Slack/reviews/" }],
    "maxReviewsPerProduct": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("arcadium/capterra-reviews").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 '{
  "startUrls": [
    {
      "url": "https://www.capterra.com/p/135003/Slack/reviews/"
    }
  ],
  "maxReviewsPerProduct": 20
}' |
apify call arcadium/capterra-reviews --silent --output-dataset

```

## MCP server setup

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

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/bgXFbxCCM9chb2nE9/builds/eaRScnsC2y8ZpKVhv/openapi.json