Documentation Python quickstart Blog Free tools Enterprise solutions hello@quanticdata.ioLog in
All collectors

Trustpilot scraper API

Company data · v1.2.0 · trustpilot_reviews

$0.002 / review

$2.00 / 1K · pay per delivered review

A Trustpilot scraper API that turns a company's public review profile into rows: star rating, title and full text, publish and experience dates, the reviewer's name, country and review count, the verified label, and the company's reply with its date. You pass the company's domain — wise.com, not a Trustpilot URL — and filter by stars or sort by recency.

$0.002 per delivered review · $2 free every month · Failed runs never billed

What it does

What a Trustpilot scraper API does

Trustpilot pages ship their state as structured JSON inside the page itself, and that is what this collector reads — so a rating is a number and a date is a date, never a regex over displayed text. The reply thread matters as much as the review: a complaints dataset without the company's answers tells you who is angry but not who cares, and here both sides arrive on the same row.

The star filter is the practical half. Pulling only the 1-star reviews of a competitor is a churn-reasons dataset; pulling your own is a support backlog. Either is one call with stars set, priced per delivered review, and the run notes carry the profile's TrustScore and total review count so every export is anchored to the profile it came from.

Inputs

The whole request. Anything you leave out falls back to the default shown in the catalog.

InputTypeRequiredWhat it does
domainstringyesThe reviewed company's domain, e.g. wise.com (not the Trustpilot URL).
sortstringnoReview order (default recency). One of: recency, relevance.
starsintegernoOnly reviews with this star rating (1–5). Omit for all.
countrystringnoISO 3166-1 alpha-2 code — proxy exit geo. Omit for the default pool.
max_resultsintegernoHow many reviews to deliver at most (1–100). You pay only for delivered reviews.

Outputs — 25 fields, one row per review

What one review looks like

Every delivered review carries these fields. Nullable means the source did not publish it — the field stays empty instead of being guessed.

FieldTypeWhat it holds
rankinteger1-based position in the requested order.
pageintegerProfile page the review came from.
idstring · nullableTrustpilot review id.
titlestring · nullableReview title.
textstring · nullableFull review text.
ratinginteger · nullableStar rating (1–5).
datestring · nullablePublish date (ISO 8601).
experience_datestring · nullableDate of the reviewed experience (ISO 8601).
reviewerstring · nullableReviewer display name.
reviewer_countrystring · nullableReviewer country code.
reviewer_reviewsinteger · nullableHow many reviews the reviewer has written.
verifiedbooleanTrue when Trustpilot marks the review as verified.
likesintegerUseful votes on the review.
replystring · nullableCompany reply text, when present.
reply_datestring · nullableCompany reply date (ISO 8601).
urlstring · nullableDirect link to the review.
languagestring · nullableLanguage of the review (ISO code).
sourcestring · nullableHow the review was collected, as Trustpilot labels it (Organic, Invited…).
verification_levelstring · nullableTrustpilot's verification label for the review (verified, invited, not-verified…).
updated_datestring · nullableWhen the reviewer last edited the review (ISO 8601), null when never.
reply_updated_datestring · nullableWhen the company last edited its reply (ISO 8601).
reviewer_reviews_same_companyinteger · nullableHow many reviews this reviewer has written about the same company.
companystring · nullableReviewed company as Trustpilot names it.
company_trust_scorenumber · nullableThe company's TrustScore at collection time.
company_reviewsinteger · nullableTotal reviews on the company's profile at collection time.

Integration

One POST, typed rows

Base URL https://api.quanticdata.io/v1, Bearer auth, the same key as every other Data API. Endpoint: POST /v1/scraper/collectors/trustpilot_reviews/run.

curl -X POST https://api.quanticdata.io/v1/scraper/collectors/trustpilot_reviews/run \
  -H "Authorization: Bearer $QD_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"domain":"wise.com","sort":"recency","max_results":20}'

Example response

POST /v1/scraper/collectors/trustpilot_reviews/run
$ curl $QD/trustpilot_reviews/run \
    -H "Authorization: Bearer $QD_API_KEY" \
    -d '{"domain": "wise.com", "sort": "recency", "max_results": 20}'
{ "status": "done", "count": 20,
  "results": [
    {
      "id": "…",
      "title": "…",
      "text": "…",
      "rating": … } ],
  "cost": 0.04 }
# 20 reviews × $0.002 · nothing delivered, nothing charged

Try it

Trustpilot reviews, running now

Change the input and run it against the live collector — nothing to install, no sign-up.

Run it from your own code, on your own inputs

Same collector, same rows — $2 of free API credit every month, no card.

Get my free API key
Trustpilot scraper API: from domain and sort, QuanticData reads the Trustpilot reviews and returns one row per review with rating, title and text, at $0.002 per delivered review.
You send domain and sort; the run goes out through a residential exit and comes back as reviews with rank, page and id — 25 fields on every row — and you are billed $0.002 for each review actually delivered, nothing for a run that delivers none.
$0.002 / review1,000 reviews on the free $2 every month
Semantic inputdomain, sort, stars — no URL lists
Up to 100reviews per run, pagination handled for you

Pricing

Trustpilot scraper API pricing

$0.002 per delivered review. A run that delivers nothing costs nothing: blocked pages, challenges and retries are on us, and the $2 monthly allowance covers about 1,000 reviews before you spend anything.

$0.002per delivered review$2 per 1,000 delivered reviews
1,000 reviewson the free allowance$2 every month, no card
Zero rowszero chargeblocks, captchas and retries are on us
−30%on volume tiersthe catalog returns your key's price

Same wallet, same key and same $2 monthly allowance as every other Data API. Prices are launch pricing read live from the billing config — GET /v1/scraper/collectors returns the price your key actually pays.

What people build with the Trustpilot scraper API

Three shapes of work this endpoint was designed around.

Churn and complaint mining

Filter a competitor's profile to 1–2 stars and you have the reasons customers leave them, written by the customers themselves — sortable by date to see whether a problem is historic or current.

Reply-rate benchmarking

The reply and reply_date columns make response behaviour measurable: share of reviews answered and how fast, across every brand you track.

Reputation monitoring

Re-run with sort recency and diff against the previous pull: new reviews, rating drift and fresh replies land in your warehouse on your schedule.

Trustpilot scraper API versus rolling your own

The differences that actually cost time when you build this in-house.

DIY scraperThis collector
What you passA Trustpilot page URL to scrape and parseThe company domain — the collector finds and reads the profile
FieldsWhatever survives your selectors after the next redesignThe page's own JSON: exact ratings, dates, verification, replies
CoverageOne page unless you build paginationPaginates to max_results, star-filtered server-side
Trustpilot scraper API: the POST to the trustpilot_reviews collector, 20 reviews delivered and the bill, 20 × $0.002 = $0.04 in usage.cost_usd; zero reviews would cost $0.
The same call you would paste into a terminal: a Bearer key, domain, sort and stars in the body, and back the envelope every QuanticData endpoint returns — type, message, payload — where count is how many reviews arrived and usage.cost_usd is $0.04, which is 20 × $0.002. A run that delivers nothing costs nothing. The key is good for 60 req/min on the free tier.

Sources and standards

The platform documentation and standards this collector is built against — check any claim on this page against the primary source:

FAQ

Questions we get about the Trustpilot scraper API.

Something else? Ask us

Does it need a Trustpilot account or API key?

No. It reads public review profiles only — nothing is logged in, and usage is metered on the QuanticData key you already hold, like every collector in the catalog.

How many reviews can one run deliver?

Up to 100 per run (20 per profile page), newest or most relevant first. For a full historical export, run with sort recency and page through runs — you pay per delivered review either way.

Can I get only negative reviews?

Yes — set stars to 1 (or any single rating 1–5) and the profile is filtered server-side before rows are delivered, so a 1-star pull does not burn budget on 5-star rows.

Do I get the company's responses too?

Yes: reply and reply_date ride on each review row when the company answered, which is what makes response-rate and response-time measurable.

Is there a free Trustpilot scraper API?

Every account gets $2 of credit every month with no card, which is about 1,000 delivered reviews on this endpoint at $0.002 each. It renews monthly, and a run that delivers nothing is never billed — so a failed or blocked attempt does not eat the allowance.

How much does one run cost?

Multiply the rows you actually receive by $0.002. A run capped at 100 reviews — the maximum for this collector — costs $0.2 if every row comes back, and less when the source has fewer. Volume tiers take up to 30% off, and GET /v1/scraper/collectors returns the price your key actually pays.

Run the Trustpilot scraper API now

$2 of free credit every month, no card. Your key returns its own prices from GET /v1/scraper/collectors.

Run in dashboard
Illustration: three coloured zones of the page that is read (Trustpilot reviews) turn into clean JSON with the fields rating, title and text; 25 fields on every row.