ForHosting KIT · Web Scraping & Monitoring

Extract reviews

Customer opinions carry real signal, but they're locked inside paginated widgets, star icons rendered as CSS, and review counts that only update after a page reload. This review extraction API opens the page and turns that scattered opinion into structured JSON — rating, review text, author, and date — ready for analysis instead of manual copy-pasting.

● BetaPer request + per URL$0.046

Run — $0.046 + $0.0145/URL How it works & API

Use it from WebAPIEmailApp soonTelegram soon

Run it online

Run this on our servers with your account. Free tools run in your browser; this one bills your KIT balance per the price above.

What makes reviews harder to extract than they look

A star rating is often not text at all — it's five icons with a CSS class that fills a fraction of a star, meaning the number never appears anywhere in the raw HTML. Review text frequently loads a page at a time behind a 'load more' button, and the reviewer's name, verified-purchase badge, and helpful-vote count each live in their own inconsistent markup. The reviews-extract endpoint handles this by rendering the page fully and reading the rating and text the way a visitor would see them, not by guessing at a number buried in a class name.

The request and the response

Send the product page URL to POST /web/reviews-extract and receive a task_id right away while the task runs asynchronously. The result is a structured list of reviews, each with its rating, body text, and available metadata such as author and date, plus the page's overall average rating and review count where the page exposes them — delivered through a signed webhook or a signed link valid for 24 hours.

Who pulls reviews at scale

Brand teams monitor sentiment across their own listings and a competitor's without reading every review by hand. Market researchers build datasets of customer language to understand what features people actually mention. Marketplaces audit for suspicious review patterns across sellers. In each case the volume of reviews makes manual reading impractical the moment a product passes a few dozen ratings.

Reviews as a research artifact

Structured customer reviews became a mainstream commerce feature in the early 2000s, and they've since grown into one of the richest free-text datasets available on the open web — genuine, unscripted language about how a product performs in practice. That richness is exactly what makes reviews useful for far more than star-rating averages: sentiment trends, recurring complaints, and feature requests all live inside the text itself.

Automating an ongoing read

Because only successful extractions are billed — three automatic retries before a clear failure — this endpoint fits naturally into a recurring job that re-checks review pages weekly or monthly to track how sentiment shifts over time, feeding a dashboard or a sentiment model without anyone opening the page by hand.

What you can do with it

Brand sentiment tracking

A company pulls reviews from its own retail listings each month to spot recurring complaints before they show up in support tickets.

Competitive product research

A product team reads what buyers say about a rival's item to find feature gaps worth building next.

Marketplace trust and safety

A platform scans seller review patterns for signs of manipulation, like a burst of five-star reviews in a single day.

Voice-of-customer datasets

A market research firm builds a text corpus of genuine customer language for a client's category analysis.

FAQ

Can this scrape product reviews API extract star ratings, not just text?

Yes, each review's numeric rating is extracted along with its text and any available author or date metadata.

Is there a free tier for the review extraction API?

There's no free tier — free tiers get abused and slow everyone down. Access runs on a prepaid ForHosting KIT balance: top up from $10.00 (it never expires) and each request is charged at its published price, so a call with no balance returns HTTP 402. No subscription, no tokens, no invented credits, and a failed task is never charged.

What does the review extraction API cost?

It's $0.046 per request plus $0.0145 per URL, and you're only billed when the task succeeds.

Does it capture the overall average rating and review count too?

Yes, when the page displays an aggregate rating and total review count, both are included alongside the individual reviews.

Can I extract reviews from multiple product pages at once?

Yes, submit multiple URLs in one batch and each is processed and priced individually at the per-URL rate.

What happens if a review page doesn't load correctly?

The task retries automatically up to three times, then returns a clear error with no charge if it still fails.

How do I get the extracted reviews back?

Through a signed webhook, recommended for automated pipelines, or a signed link valid for 24 hours.

Are the reviews I extract used to train any model?

No, extracted data is deleted after the retention window and is never used for training purposes.

For developers — API access

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

API endpoint

POSThttps://api.kit.forhosting.com/web/reviews-extract

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, and soon from our app, email and Telegram.

Call it from your stack

curl -X POST https://api.kit.forhosting.com/web/reviews-extract \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d &#39;{"url":"https://ejemplo.com"}'

const res = await fetch("https://api.kit.forhosting.com/web/reviews-extract", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "url": "https://ejemplo.com"
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/web/reviews-extract",
    headers={"Authorization": f"Bearer {os.environ[&#39;KIT_KEY']}"},
    json={
    "url": "https://ejemplo.com"
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/web/reviews-extract", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => &#39;{"url":"https://ejemplo.com"}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"url":"https://ejemplo.com"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/web/reviews-extract", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "url": "https://ejemplo.com"
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "web.reviews_extract",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Pricing

Per request$0.046

Per URL$0.0145

Published price — no tokens, no invented credits. A failed task is never charged.

Limits

`timeout_sec`	30
`max_crawl_pages`	25

Errors

HTTP	Code	Meaning
`401`	`unauthorized`	Missing or invalid API key.
`402`	`insufficient_balance`	Your balance doesn't cover the task price.
`404`	`unknown_type`	That task type doesn't exist.
`429`	`rate_limited`	Too many requests. Use the webhook instead of polling.
`422`	`task_failed`	The task failed after 3 retries. You are never charged for it.

Read the full KIT documentation →