How to Export Trustpilot Reviews Past the 200-Review Limit

To export more than 200 Trustpilot reviews, split the business into filter slices that each hold 200 reviews or fewer, page through every slice, and merge the results on review_id. Trustpilot serves at most 10 pages of 20 reviews for any one filter combination, but each star rating, language and text search is a separate combination. Scavio's Trustpilot reviews endpoint takes those filters, returns 20 reviews per call for 2 credits, and reports total_filtered so you know when a slice is complete. For most businesses that means every review. For a big brand it means thousands more than 200, not the full history, and this page shows exactly how far it reaches.

The question comes up constantly. From r/scrapingtheweb in September 2026: "I need way more than 200 reviews for one company. like ideally the full history or at least a few thousand. is it really impossible???" Here is the honest answer, with numbers from live calls we made on October 10, 2026.

Step 1: see how the reviews split

One call to the business endpoint returns the rating distribution and the review count per language. That is your slicing plan.

curl -s https://api.scavio.dev/api/v1/trustpilot/business \
  -H "Authorization: Bearer $SCAVIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"domain": "www.hostinger.com"}'

For Hostinger this returned 73,018 reviews across 71 languages: 44,288 English, 8,716 Spanish, 8,581 Portuguese and 3,326 French among them, with 5,033 one-star reviews. That is a hard case, which is why we picked it.

Step 2: export every slice

A slice is complete when it has 200 reviews or fewer. If a language has 200 or fewer, take it whole. If it has more, split it by star rating.

import csv, os, requests

API = "https://api.scavio.dev/api/v1/trustpilot"
H = {"Authorization": f"Bearer {os.environ['SCAVIO_API_KEY']}"}
DOMAIN = "www.hostinger.com"

def post(endpoint, body):
    r = requests.post(f"{API}/{endpoint}", headers=H, json=body, timeout=90)
    r.raise_for_status()
    return r.json()["data"]

def export_slice(filters, rows):
    for page in range(1, 11):
        data = post("reviews", {"domain": DOMAIN, "page": page, **filters})
        for rv in data["reviews"]:
            rows[rv["review_id"]] = rv          # dedupe across slices
        if page >= data["max_page"] or data["count"] < 20:
            return data["total_filtered"]

profile = post("business", {"domain": DOMAIN})
rows = {}
for lang in profile["languages"]:
    if lang["review_count"] <= 200:
        export_slice({"language": lang["code"]}, rows)
    else:
        for star in range(1, 6):
            export_slice({"language": lang["code"], "stars": [star]}, rows)

with open("reviews.csv", "w", newline="") as f:
    w = csv.writer(f)
    w.writerow(["review_id", "rating", "language", "published_at", "verified", "title", "text", "reply"])
    for rv in rows.values():
        w.writerow([rv["review_id"], rv["rating"], rv["language"], rv["published_at"], rv["verified"],
                    rv["title"], rv["text"], (rv["reply"] or {}).get("text", "")])
print(len(rows), "unique reviews")

Each review also carries its experience date, likes, verification source and the reviewer's public name and country, so add columns as you need them.

How far slicing actually reaches

This is the part most tools gloss over, so here are the measured numbers for Hostinger.

Each slice returns its newest 200. The 1-star English slice holds 3,788 reviews, so you get the newest 5% of it, covering the last eight weeks. Adding a text search narrows the slice, and the narrower slice reaches more than a year further back. Searches and topic filters overlap, which is why the script deduplicates on review_id.

For this business, the star-by-language slices add up to at most 7,613 reviews, about 10% of the total.

A user in that same Reddit thread put it accurately: if one slice already holds more than 200, you will miss reviews. Slicing gets you more, not everything.

The long tail is a different story. In a 250-business sample we took the same day, 172 businesses (69%) had 200 reviews or fewer, so plain paging returned every review. If you are exporting competitors in a niche rather than one global brand, you will usually get all of them.

Count reviews you cannot export

total_filtered is exact even when the slice is larger than 200, so counts never hit the cap. One call with date_range: "last30days" showed Hostinger received 944 reviews in the last 30 days across all languages. That is review velocity from a single request, useful for spotting review campaigns or a sudden drop.

What it costs

Every call is 2 credits and returns up to 20 reviews. On the Growth plan billed yearly ($2 per 1,000 credits) that is $0.20 per 1,000 reviews. A complete 200-review slice is 10 calls, $0.04. Hostinger's full slice ceiling of 7,613 reviews is about 381 calls, roughly 762 credits or $1.52, which fits in the $30 Project plan's 7,000 monthly credits. Calls took 2 to 6 seconds each in our run, so this is for scheduled exports, not instant ones.

The limits, stated plainly: 200 reviews per filter combination; no full review history for large brands; reviewer data is limited to what Trustpilot shows publicly. If you manage the business yourself, Trustpilot Business can export your own reviews to CSV directly.

Get 50 free credits, no card, enough for 500 reviews, and try the reviews call in the playground.

Reference: Trustpilot API overview · reviews · business · search