Capterra Reviews Scraper

Yes — Capterra reviews are public data. We read the same review pages any visitor opens: no login, no private area. What you do with the text afterwards is on you, so quote fairly. More on the legality of web scraping.

No login required. No account to sync, no cookie to paste, no Chrome extension to install. Paste a product URL and the reviews start coming back — Capterra shows them to every visitor, and so do we.

45 data points per review. Title, date, the overall rating and four sub-ratings, likelihood to recommend, pros, cons, comments and the vendor's reply — plus the reviewer's job title, industry, company size and how long they've used the product.

About 200 reviews a minute. A product with a thousand reviews is done in five minutes — less time than it takes to read the three angriest ones yourself. Paste a whole list of rivals and walk away.

Yes — set Rating to 1-2 stars or 1-3 stars. A review you filter out is never billed, so you pay for the complaints and nothing else. On capterra.com, Sort By Lowest Rating puts the worst ones first.

Yes — whenever the reviewer shares it. You get the products they switched from, their reasons for switching, the alternatives they weighed and why they picked this one. Run it on a rival and you'll see who it wins customers from, and how.

Yes — by company size, reviewer's role, length of use and frequency of use. Keep only admins at 51-200 employee companies who've used the product for 2+ years, say. Role and frequency filters work on capterra.com only.

Yes — 23 of them, from capterra.co.uk to capterra.com.br. Reviews come back in the language the site shows. Regional sites sort by Most Recent or Most Helpful only, so reach for the Rating filter to find the low scores there.

Yes — set Newer than and schedule the run. Newer than keeps reviews written since a date or a window like the last 7 days, so a weekly run sends only the fresh ones. Every new complaint about a rival, in your sheet by Monday morning.

Just about anywhere you already work. Google Sheets, Make, n8n, Amazon S3, email, webhooks — plus our MCP server, so Claude or ChatGPT can launch a run and read the results for you. CSV, Excel and JSON downloads too. See all integrations.

URL, such as https://www.capterra.com/p/186596/Notion/reviews/. Paste thousands at once or upload a CSV; duplicate inputs are skipped. 10 settings shape the run: see them in the playground.

45 data attributes per review, each with its description and an example: see the full list.

No. Duplicates are removed, and you only pay for unique results.

As fresh as your run: each run collects the data from the site at the moment it runs, nothing comes from a stored database.

CSV, Excel or JSON from the dashboard, through the API, or sent after every run to Google Sheets, Amazon S3, an SFTP server, a webhook or by email.

7 days on the free plan, 28 days on paid plans. Then they are deleted. Download or deliver what you want to keep.

Around 200 reviews a minute for one squid. Your plan's slots run several squids at the same time.

100.00% of its runs had no incident over the last 90 days (0 incidents, 100% fixed). Every day is on this page.

Our team fixes the scraper: every scraper on lobstr.io is built and maintained by us. How we measure.

Yes, on paid plans: every hour, every day, every weekday or on a custom schedule, in your time zone.

Yes: set the most results per task and per run in the settings. The run stops there and so does the bill.

1 credit per result. The playground shows the price as you pick them.

Yes. The free plan gives 100 credits every month, 100 results with this scraper, with exports capped at 30 rows.

Every month a plan gives credits, which pay for results, and slots, which set how many squids run at the same time. Starter: $20 for 10,000 credits; Pro: $100 for 100,000 credits; Team: $500 for 1,000,000 credits. Upgrades start right away and are prorated; downgrades and cancellations take effect at the end of the cycle.

No. Your credits refresh every month with your plan.

You choose, per squid: pause and pick up where it stopped, or end the run. To keep going, upgrade or reset your billing cycle: your plan renews right away and your credits come back. Auto Billing Reset does it for you when your usage crosses a threshold you set.

Yes: paying yearly takes 20% off every plan.

A monthly plan: within 10 days of the charge, if no credit was used in that period. A yearly plan: within 30 days, in full if no credit was used, otherwise minus one month. Cancel from your billing page, then write to contact@lobstr.io. The details are in the terms of use.

Collecting publicly available data is generally allowed, but you choose what you collect and you are responsible for how you use it. Our terms of use (article 6) ask every user to respect the rights of the sites, not to extract substantial parts of a database, not to access confidential data and to follow personal data law such as the GDPR. This is not legal advice.

When results contain personal data, you are the data controller and lobstr.io, a French company, processes them on your behalf, under our personal data agreement. You need a lawful basis for what you collect, must inform the people concerned and honor their requests.

Results: 7 days on the free plan, 28 days on paid plans, then they are deleted; you can delete them sooner. Your account data: see the privacy notice.

Yes, through the REST API at https://api.lobstr.io/v1, with your key from the dashboard. The playground’s Code tab writes the calls for your settings, in cURL and Python. The documentation has the full reference.

Yes. Add our MCP server, https://mcp.lobstr.io/mcp, to Claude, ChatGPT, Cursor or any MCP client and sign in with lobstr.io. Your agent shows the cost and asks you before a run spends credits. The playground’s Agent tab gives you a prompt.

No. Credits pay for results, not for requests.

Yes. Point a webhook at your server and lobstr.io calls it when a run succeeds or fails.

Yes, per endpoint: 120 requests a minute on squids and runs, 90 on tasks, 2 a second on results. Above that the API answers 429 with a Retry-After header.