G2 Reviews Scraper - $1.70 per 1,000, No API Key
Pricing
Pay per event
G2 Reviews Scraper - $1.70 per 1,000, No API Key
$1.70 per 1,000 reviews, against the $1.00 to $6.49 charged by other G2 review scrapers with an active user base. Pull real G2 software reviews for any product: rating, title, full review text, reviewer, date and review URL. No G2 account, no API key, no captcha wrangling.
Pricing
Pay per event
Rating
0.0
(0)
Developer
Dami's Studio
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
G2 Reviews Scraper & API
Pulls software reviews off G2.com by product URL or slug. Give it notion or
https://www.g2.com/products/notion/reviews and you get every review G2 publishes for that product:
star rating, title, pros, cons, problems solved, the reviewer's role and company size, and the date.
Measured on real runs: 1,000 reviews in 39 seconds, 251 in 11 seconds. No G2 account, no API key, no cookie to paste in.
Price
$1.70 per 1,000 reviews ($0.0017 each), plus $0.002 each time a run starts. Flat rate — no volume tiers, no plan gates. For context, the other G2 review scrapers on the Apify Store with an active user base run from $1.00 to $6.49 per 1,000, resolved live on 2026-08-10 at each one's lowest volume tier rather than its headline free-tier rate.
You are charged per review actually returned. A run that finds nothing charges nothing beyond the start fee.
What you get
| Field | Notes |
|---|---|
productName, productSlug, productUrl | the product the review belongs to |
reviewId, reviewNumericId, reviewUrl | stable ids, and a direct link to the review |
title | the reviewer's own headline |
rating | 1–5 stars |
reviewText | the full body |
pros, cons, problemsSolved | G2's three structured prompts, kept separate |
reviewerName, reviewerRole | as G2 displays them |
companySize | e.g. "Mid-Market (51-1000 emp.)" |
publishedAt, publishedAtRaw | ISO 8601, plus G2's original string |
Coverage across a real 1,000-review run: everything above at 100%, except companySize at
67% — G2 simply does not show it for every reviewer. Where it is missing you get null, not a
guess.
Input
{"products": ["notion", "https://www.g2.com/products/slack/reviews"],"maxItems": 500}
products— slugs or full G2 review URLs, mixed freely.maxItems— stop after this many reviews. Leave it out for everything available.
Run it with no input and you get a single labelled sample row, uncharged, so you can see the shape before spending anything.
How it holds up
G2's review pages sit behind DataDome, which blocks plain HTTP clients. This actor does not fight that — it reads G2's own per-product review feed, which serves the same reviews and is not walled. That is why it is fast and why it does not need a browser, a proxy budget or a login.
The practical ceiling is about 5,000 reviews per product, which is what the feed carries. For most products that is the entire review history.
What this does not do
- No product search. You bring the product; it does not discover products by category or query.
- No reviewer contact details. G2 does not publish them and neither does this.
- No vendor replies or review comments. Not in the feed.
- No G2 rating breakdowns, pricing tabs or comparison data. Reviews only.
- Products with fewer than a handful of reviews may return everything G2 has and stop early. That is the product, not a failure.
FAQ
Do I need a G2 login or API key? No. Nothing to authenticate, nothing to configure.
How many reviews can I get for one product? Up to roughly 5,000, which is the depth of G2's feed. Notion, Slack and similar large products hit that ceiling; smaller products return their full history.
How fast is it? 1,000 reviews in 39 seconds in testing. 251 in 11 seconds.
What does it cost to scrape 1,000 G2 reviews? $1.70, plus the $0.002 start fee.
Can I get reviews for several products in one run?
Yes. Pass as many slugs or URLs as you like in products; each review row carries its own
productName and productSlug.
Is the review text complete or truncated?
Complete. reviewText is the full body, and pros, cons and problemsSolved are kept as separate
fields rather than concatenated.
What happens if a product URL is wrong? You get an uncharged diagnostic row naming the problem, not a silent empty run.
Can I export to CSV or Excel? Yes — Apify exports the dataset as JSON, CSV, Excel or XML, and there is a REST endpoint for the same data.