Capterra Profile Scraper

The vendor's side of a software product, read from its Capterra page: the full product description, the aggregate rating and the review count behind it, the platforms it lists, the category Capterra files it under, and the product Q&A.

That last one is the reason this Actor exists as its own thing. The profile page carries no reviews and the reviews page carries no Q&A. Neither is a subset of the other, so the two are two reads rather than one read with an option — and folding the profile into a review walk would mean a second request per product charged as though it were free.

Accepted input

productUrls is required and takes one or more Capterra product pages, one per line. A full link works:

https://www.capterra.com/p/147657/monday-com/

So does the pair inside it, 147657/monday-com. The number on its own does not. A Capterra product is addressed by a number and a name and neither can be derived from the other, so a bare 147657 is refused before any request is made rather than after one has been paid for. The name half is case sensitive — Capterra spells them monday-com, GitLab, Structure, Asana-PM — which is why the practical way to fill this field is to paste the url column from Capterra Category Scraper rather than to type anything.

{
  "productUrls": [
    "https://www.capterra.com/p/147657/monday-com/",
    "159806/GitLab"
  ]
}

Response fields

One row per product. This is the row that run produced for the first entry, with the description and the Q&A shortened for length:

{
  "product_id": "147657",
  "slug": "monday-com",
  "url": "https://www.capterra.com/p/147657/monday-com/",
  "name": "monday.com AI Work Platform",
  "description": "monday.com empowers teams to manage the entire project lifecycle in one place with precision. It provides advanced capab ...",
  "application_category": "BusinessApplication",
  "operating_systems": [],
  "rating": 4.6,
  "rating_best": 5,
  "rating_worst": 1,
  "review_count": 6095,
  "category_slug": "project-management-software",
  "category_name": "Project Management Software",
  "category_url": "https://www.capterra.com/project-management-software/",
  "breadcrumbs": [
    { "position": 1, "name": "Home", "url": "https://www.capterra.com/", "slug": null },
    {
      "position": 2,
      "name": "Project Management Software",
      "url": "https://www.capterra.com/project-management-software/",
      "slug": "project-management-software"
    },
    { "position": 3, "name": "monday.com AI Work Platform", "url": null, "slug": null }
  ],
  "faq": [
    {
      "question": "What problems does monday.com AI Work Platform solve?",
      "answer": "monday.com AI Work Platform solves scattered task ownership, weak cross-team vis ..."
    }
  ]
}

category_slug runs the other way to the rest of this family. Every other address here points from a category down to a product; this one points from a product back up to the category it belongs to, and it is exactly the value Capterra Category Scraper takes. Given one product, that is how you reach its competitors.

faq is Capterra's own product Q&A, republished whole. Nine entries on the product above, and none of them anywhere on its reviews page.

operating_systems is frequently an empty list, as it is above. That means the page stated none, not that the product runs nowhere.

rating_best is 5 and rating_worst is 1, on every product. The scale is published anyway, because a review row in this family carries a would-you-recommend score out of 10 beside a star rating out of 5, and an assumed scale is how the two get averaged together.

Behaviour on partial results

A product address that no longer resolves is logged and skipped, and the run continues with the next one. That is not a rare case here: Capterra product numbers rot, and the number published for one well-known product in older public write-ups answers 404 today. Losing nineteen good rows to one dead address would be the wrong trade.

An entry that is not a product address at all — a bare number, a product name — is logged and skipped without a request being made, and the log says what a valid address looks like.

Frequently asked questions

Why is there no review text on these rows? Because there is none on the page. Capterra's profile carries the rating summary and an empty review list; the reviews live on their own page. Run Capterra Reviews Scraper with the same productUrls for those.

Why did one product take thirty seconds and the next take three? Because a page Capterra is already holding answers immediately and one that has to be fetched fresh does not. Two live profile reads on 2026-08-23 took 33.9s and 32.8s; other endpoints on the same site answered in under two seconds the same minute. A run that appears to pause is behaving normally.

Can I pass just the product number? No, and that is a property of Capterra rather than a restriction added here — /p/147657/ on its own is not a page. Pass the whole address, or the url column from a category export.

Why is the slug capitalised on some products? Because Capterra capitalises it. GitLab and Structure are the real spellings of those addresses and lowercasing them produces a 404, so nothing in this Actor changes the case of what you paste.

Is a Capterra account, cookie or API key required? No. No account, session cookie or key of any kind is supplied to the Actor or needed by it.

Related Actors

Capterra Category Scraper walks a category in ranked order and publishes the address of every product in it — including the ones this Actor takes.

Capterra Reviews Scraper reads the same products' reviews, with pros and cons kept as separate answers and the reviewer's job title and industry on every row.