Best Trustpilot Reviews APIs: Only 2 Get Past 200 Reviews [Tested]

⚡ 15-Second Summary

1. The problem: Trustpilot locks anonymous visitors out after page 10 of reviews, 20 reviews a page. Most APIs stop at exactly 200 reviews per business because of it.
2. How I tested: 5 APIs, 5 businesses, 200 reviews each as the baseline (1,000 total), then 1,000 per business (5,000 total) for the APIs that cleared the wall. Every raw run is in a public repo.
3. lobstr.io: 5,000/5,000, 0 duplicates, 100% field coverage, 35 fields per review. $2.00 per 1K reviews on the $20 plan, $0.50 per 1K at volume. Async workflow, so expect five API calls before you see a review.
4. Apify via memo23: 5,000/5,000, 0 duplicates, $0.63 to $0.66 per 1K measured. Faster than lobstr.io in a single run, but no company-level fields and no filters.
5. DataForSEO: $0.038 per 1K, the cheapest by a mile, but hard-capped at 200 reviews per business with no way around it.

The official API is worse in a different way: you can't even start without a waitlist approval. And the third-party APIs that promise "all reviews" mostly don't deliver them.

So I tested the main Trustpilot reviews APIs side by side, same businesses, same request shape, same day where possible.

For reproducibility, everything is in a public repo, down to the raw responses and the credit snapshots.

But first, the question everyone asks... why not just use the official Trustpilot API?

Does Trustpilot have an official reviews API?

Yes. Trustpilot offers several APIs (Business Units, Product Reviews, Service Reviews, Data Solutions), but most of them only let you read and reply to your own reviews.

curl -X GET "https://datasolutions.trustpilot.com/v1/business-units/{businessUnitId}/reviews" \
  -H "apikey: YOUR-API-KEY"
f

A sample response from the official docs:

{
  "reviews": [
    {
      "id": "507f191e810c19729de860ea",
      "stars": 4,
      "title": "Great Service!",
      "text": "I had a wonderful experience.",
      "language": "en",
      "isVerified": true,
      "createdAt": "2023-12-31T12:00:00Z",
      "updatedAt": "2023-12-31T12:00:00Z",
      "experiencedAt": "2023-12-31T12:00:00Z",
      "source": "organic",
      "reviewedLocationName": "Pilestraede 58"
    }
  ],
  "nextToken": "..."
}
f

The catch is access. There is no sign-up and no self-serve API key.

You register your interest on a waitlist, Trustpilot decides whether your use case deserves approval, and there is no timeline for that decision.

Unless you're an enterprise or a non-profit, your chances are thin. So I excluded it from the comparison on accessibility, not capability.

What about Trustpilot's internal API?

Trustpilot's own review pages fetch their data from an internal Next.js endpoint.

Open DevTools, switch to the Network tab, click to page 2 of any listing, and you'll see a request like this one for The Pearl Source:

/_next/data/businessunitprofile-consumersite-2.7799.0/review/www.thepearlsource.com.json?page=2&businessUnit=www.thepearlsource.com
f

The response is clean JSON with everything the page renders.

Tempting, but two problems.

It's an undocumented internal endpoint, so the build number in the path and the response shape can change without notice.

And it hits the same wall as your browser does: Trustpilot forces a login after page 10, so the internal API gives you a nicer JSON shape and the same 200 reviews.

Good for understanding how Trustpilot loads reviews. Not something I'd build a production pipeline on.

That leaves two routes: build your own scraper, or use a third-party Trustpilot reviews API.

Building your own scraper sounds cool for the nerds, but keeping it alive against Trustpilot's page changes, anti-bot measures, and that login wall is where it turns into maintenance hell.

For this article I went with third-party APIs.

How I picked and tested the APIs

I went through vendor docs, developer forums, Reddit threads and GitHub issues to build the long list, then cut it with six elimination rules:

1. No self-serve access: waitlist, sales call or no trial
2. Run failure: below 50% success rate, or breaks mid-run
3. No usable docs: you can't build a working request from the documentation alone
4. Unclear pricing: cost per 1K reviews can't be calculated
5. Wrong data: doesn't return review-level data
6. Dead or abandoned: no response, broken infrastructure, no maintenance

Five APIs survived: lobstr.io, Apify, DataForSEO, Outscraper and OpenWeb Ninja.

How I tested the APIs

Every API got the same 5 businesses: The Pearl Source, SHEIN, Temu, AliExpress and Halara.

The baseline run asked for 200 reviews per business, 1,000 in total.

Any API that cleared the baseline without hitting a ceiling then got a depth run at 1,000 reviews per business, 5,000 in total.

I judged each API on six things:

1. Reliability: did it return what I asked for, every time?
2. Data quality: was the data accurate and complete?
3. Cost: what did 1K reviews cost?
4. Speed: how fast did the run complete?
5. Scalability: could it collect more than 200 reviews from one business?
6. Usability: how much work is the integration?

Here is how the five stacked up:

Best Trustpilot reviews API: lobstr.io

1. User rating: 5/5 (Capterra, 33 reviews, as of August 13, 2026)
2. API type: Async
3. Best for: Collecting every review a business has, at scale

What is lobstr.io?

Pricing

Cost per 1K reviews

1. $2.00 per 1K on the $20 Starter plan
2. $0.50 per 1K at volume

Data

One review object from a live run:

{
  "id": 11313,
  "object": "result",
  "run": "4c2e07bd3b9b4c9386661edb8ef58174",
  "author_id": "5cf2ae01d0f74610485343de",
  "author_image": null,
  "author_name": "customer",
  "business_unit_id": "4be2ffa600006400050873c2",
  "company_category": "Jewelry Store",
  "company_name": "The Pearl Source",
  "company_page_url": "https://www.trustpilot.com/review/www.thepearlsource.com",
  "consumer_country_code": "GB",
  "consumer_reviews_on_domain": 1,
  "date_published": "2026-07-22T08:44:49Z",
  "experience_date": "2026-07-21T22:00:00Z",
  "functions": null,
  "is_author_verified": false,
  "is_review_verified": true,
  "likes": 0,
  "native_id": 11313,
  "number_of_reviews": 7,
  "owner_reply": "Knowing you're happy with your pearl earrings truly means a lot to us. Thank you for your feedback.",
  "owner_reply_date": "2026-07-23T01:22:26Z",
  "owner_reply_updated_date": null,
  "page_number": 2,
  "rating_value": 5,
  "report": null,
  "review_body": "Very nice and delicate pearl earrings. Looks amazing. I like it.",
  "review_headline": "Very nice and delicate pearl earrings",
  "review_language": "en",
  "review_link": "https://www.trustpilot.com/reviews/6a6083012bbe4c893e5ec3d3",
  "review_sentiment": null,
  "review_source": "InvitationLinkApi",
  "review_url": "6a6083012bbe4c893e5ec3d3",
  "review_verification_source": "self-invited",
  "reviews_count": 17586,
  "scraping_time": "2026-07-29T10:56:25.056Z",
  "stars": 5.0,
  "trust_score": 4.8,
  "updated_date": null,
  "verification_level": "invited"
}
f

It gives you 35 meaningful data points per review: the review itself, the reviewer, the company, verification status and Trustpilot metadata, all in one object.

Three of those weren't available in every API I tested: experience_date, verification_level and the company trust_score.

Data quality

1. Field coverage: 13/13 ground-truth fields
2. Accuracy: 20/20 reviews matched
3. Schema consistency: 0 missing fields across 1,000 reviews
4. Freshness: live data. The only differences against the ground truth were reviewer counts and reply status that changed on Trustpilot during the 8 days between the two captures

Speed

Four runs, same Squid, concurrency 1:

That's a range of 272 to 753 reviews per minute, averaging about 497.

Concurrency 1 is the default, not the limit.

Usability

lobstr.io runs on an async model: Squid → Task → Run → Results.

Here's the walkthrough, with the requests I actually ran.

1. Create or reuse a Squid

Create the Squid once, then reuse it for future runs.

curl --request POST \
  --url "https://api.lobstr.io/v1/squids" \
  --header "Authorization: Token $LOBSTR_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "crawler": "b3362ab52c6fab3d8897af79cbba380e",
    "name": "Trustpilot Reviews Job"
  }'
f

Response, trimmed to the fields that matter:

{
  "id": "0f6ac4ffea6b4b5d89b4093ffc51ef55",
  "crawler": "b3362ab52c6fab3d8897af79cbba380e",
  "concurrency": 1,
  "is_active": true,
  "to_complete": false,
  "params": {
    "max_results": null,
    "max_unique_results_per_run": null,
    "stars": "all",
    "language": "All languages",
    "replies": false,
    "verified": false,
    "topics": null,
    "search": null,
    "fetch_since": null,
    "fetch_since_timezone": null,
    "hours_back": null,
    "start_page": 1
  }
}
f

2. Add tasks and settings

A task is a Trustpilot review URL. Filters and limits live on the Squid, so every task in it shares the same configuration.

curl --request POST \
  --url "https://api.lobstr.io/v1/tasks" \
  --header "Authorization: Token $LOBSTR_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "squid": "0f6ac4ffea6b4b5d89b4093ffc51ef55",
    "tasks": [
      {
        "url": "https://www.trustpilot.com/review/www.thepearlsource.com"
      }
    ]
  }'
f

Response:

{
  "duplicated_count": 0,
  "tasks": [
    {
      "id": "b31de96590d88c602f73bc973570aa76",
      "created_at": "2026-09-04T12:25:56.433371",
      "is_active": true,
      "params": {
        "url": "https://www.trustpilot.com/review/www.thepearlsource.com"
      },
      "module": 217,
      "object": "task"
    }
  ]
}
f

"params": {
  "stars": "",                       // Star rating to filter reviews by (e.g. 1-5)
  "search": "",                      // Keyword to search for within Trustpilot review text
  "topics": "",                      // Trustpilot review topic/category to filter by
  "replies": "",                     // Whether to include business replies to reviews
  "language": "",                    // Language to filter reviews by
  "verified": "",                    // Whether to include only verified reviews
  "start_page": "",                  // Page number to start fetching results from
  "fetch_since": "",                 // Relative time window to fetch reviews from (e.g. "4w" = last 4 weeks)
  "max_results": "",                 // Maximum number of results to return
  "fetch_since_timezone": "",        // Timezone used to interpret the fetch_since window
  "max_unique_results_per_run": ""   // Cap on unique results returned per scraper run
}
f

3. Launch the run

curl --request POST \
  --url "https://api.lobstr.io/v1/runs" \
  --header "Authorization: Token $LOBSTR_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "squid": "0f6ac4ffea6b4b5d89b4093ffc51ef55"
  }'
f

Response:

{
  "id": "48d40927b5bf4437b5a9591e7c9bf210",
  "object": "run",
  "squid": "0f6ac4ffea6b4b5d89b4093ffc51ef55",
  "status": "pending",
  "is_done": false,
  "total_results": 0,
  "total_unique_results": 0,
  "credit_used": 0,
  "started_at": "2026-09-04T12:25:56Z",
  "ended_at": null
}
f

4. Poll the run status

curl --request GET \
  --url "https://api.lobstr.io/v1/runs/48d40927b5bf4437b5a9591e7c9bf210" \
  --header "Authorization: Token $LOBSTR_API_KEY"
f

5. Retrieve results

curl --request GET \
  --url "https://api.lobstr.io/v1/results?run=48d40927b5bf4437b5a9591e7c9bf210&page=1&page_size=1000" \
  --header "Authorization: Token $LOBSTR_API_KEY"
f

Response:

{
  "total_results": 1000,
  "limit": 1000,
  "page": 1,
  "total_pages": 1,
  "result_from": 1,
  "result_to": 1000,
  "next": "https://api.lobstr.io/v1/results?page=2&page_size=1000&run=48d40927b5bf4437b5a9591e7c9bf210",
  "previous": null,
  "data": [
    "1000 review objects"
  ]
}
f

Verdict

lobstr.io is the pick when review depth matters. It was one of only two APIs to get past 200 reviews per business, and the only one to do it with a perfect ground-truth match, the widest schema, and fully managed customer support.

Apify via memo23: the other API that clears 200

1. User rating: 4.8/5 (Capterra, 563 reviews, as of August 26, 2026), for the Apify platform, not the Actor
2. API type: Async (Actor run)
3. Best for: Full-depth collection if you already run on Apify

What is Apify?

Search the Store for Trustpilot and the most popular result is automation-lab/trustpilot, a community-maintained Actor like every other one there. It's not the Actor in this comparison.

In my runs it capped at exactly 200 reviews per business no matter what I requested, and one of the five businesses came back with 0 reviews and a SUCCEEDED status every time. Fine for a sample, useless for depth.

It does. It returned 1,000 reviews from each of the 5 businesses, 5,000 in total, 0 duplicates, every review attributed to the right business.

Pricing

Apify is subscription plus pay-as-you-go, with plans from $19/month to $999/month.

1. Published rate: from $0.50 per 1K reviews
2. Measured: $0.66 per 1K for the single 5,000-review run ($3.29 total), $0.63 per 1K when I split the same job into 5 runs ($3.14 total)

Data

One review object from the live response:

{
  "id": "6aa89d332cc378fe839d6ab8",
  "title": "Very quick shipping",
  "text": "Very quick shipping. Pearls came boxed excellent and looked fantastic.",
  "rating": 5,
  "language": "en",
  "source": "InvitationLinkApi",
  "isVerified": true,
  "verificationLevel": "invited",
  "publishedDate": "2026-09-15T03:19:47.000Z",
  "experiencedDate": "2026-09-06T00:00:00.000Z",
  "consumer": {
    "id": "588637d50000ff000a6f7bd9",
    "displayName": "Justme",
    "countryCode": "US",
    "numberOfReviews": 3
  },
  "reviewerName": "Justme",
  "reviewerCountry": "US",
  "reviewerNumberOfReviews": 3,
  "companyReply": {
    "text": "We're glad to hear that you were pleased with both the quick shipping and the presentation of your pearls. Thank you for sharing your feedback with us.",
    "publishedDate": "2026-09-15T19:26:32.000Z"
  },
  "url": "https://www.trustpilot.com/reviews/6aa89d332cc378fe839d6ab8",
  "businessUrl": "https://www.trustpilot.com/review/www.thepearlsource.com",
  "businessName": "The Pearl Source"
}
f

What's missing is the company level: no Trust Score, no category, no total review count. If you need those, you'll pull them from a separate source.

Data quality

1. Field coverage: 12/13 ground-truth fields. The missing one is the invited-vs-organic review type, which verificationLevel and source let you reconstruct
2. Accuracy: 19/20 reviews matched, with perfect matches on author name, country, rating, title, review text and reply text

Speed

Two configurations, same 5 businesses, 1,000 reviews each:

Usability

Apify's model is Actor → Run → Dataset. You start the Actor with an input object, poll the run until it succeeds, then read the dataset it wrote to.

https://api.apify.com/v2

1. Start the Actor run

curl --request POST \
  --url "https://api.apify.com/v2/acts/memo23~trustpilot-scraper-ppe/runs" \
  --header "Authorization: Bearer $APIFY_API_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{
    "startUrls": [
      "https://www.trustpilot.com/review/www.thepearlsource.com",
      "https://www.trustpilot.com/review/www.shein.com",
      "https://www.trustpilot.com/review/temu.com",
      "https://www.trustpilot.com/review/www.aliexpress.com",
      "https://www.trustpilot.com/review/thehalara.com"
    ],
    "maxItems": 1000,
    "filterDateRange": "all"
  }'
f

Response:

{
  "data": {
    "id": "4B9wLdy2hWaJvjto8",
    "status": "READY",
    "startedAt": "2026-09-16T07:31:46.656Z",
    "finishedAt": null,
    "defaultDatasetId": "H7poAv9kK9jiXwCKH",
    "usageTotalUsd": 0
  }
}
f

2. Poll the run status

curl --request GET \
  --url "https://api.apify.com/v2/actor-runs/4B9wLdy2hWaJvjto8" \
  --header "Authorization: Bearer $APIFY_API_TOKEN"
f

3. Retrieve the dataset

curl --request GET \
  --url "https://api.apify.com/v2/datasets/H7poAv9kK9jiXwCKH/items?format=json&clean=true&offset=0&limit=1000" \
  --header "Authorization: Bearer $APIFY_API_TOKEN"
f

Verdict

DataForSEO: the cheapest Trustpilot reviews API

1. User rating: 4.8/5 (Capterra, 15 reviews, as of August 26, 2026)
2. API type: Async (task-based)
3. Best for: Lowest-cost collection when 200 reviews per business is enough

What is DataForSEO?

Pricing

Pay-as-you-go with a $50 minimum account funding. The published rate is $0.00075 per 20 reviews, which is $0.0375 per 1K. I measured $0.038 per 1K on the actual runs.

Data

One review object from the live response:

{
  "type": "trustpilot_review_search",
  "rank_group": 5,
  "rank_absolute": 5,
  "position": "left",
  "url": "https://www.trustpilot.com/reviews/6a5cbee7d15cfd51e3c65e6b",
  "rating": {
    "rating_type": "Max5",
    "value": 5,
    "votes_count": null,
    "rating_max": 5
  },
  "verified": true,
  "language": "en",
  "timestamp": "2026-07-19 14:11:19 +00:00",
  "title": "Excellent service from ordering to delivery ",
  "review_text": "Superb service delivery from LA USA to UK in less than a week. Brilliant\nThe product is perfect and will make an ideal birthday present to match the pearl neclace I bought in May 2026 for our 30th wedding anniversary.\n\nThank you ",
  "review_images": null,
  "user_profile": {
    "name": "Stephen B",
    "url": "https://www.trustpilot.com/users/5e978a5aa222f44164634d22",
    "image_url": null,
    "location": "GB",
    "reviews_count": 14
  },
  "responses": [
    {
      "title": "Reply from The Pearl Source",
      "text": "Thank you for taking the time to share your experience. We're delighted to hear your order arrived in the UK so quickly and that your new piece is the perfect match for the pearl necklace you purchased for your 30th wedding anniversary. We truly appreciate your continued support.",
      "timestamp": "2026-07-19 22:58:42 +00:00"
    }
  ]
}
f

Data quality

1. Field coverage: 11/13 ground-truth fields, the narrowest of the five. Missing: the invited-vs-organic review type and the helpful-vote count
2. Accuracy: 20/20 reviews matched on the fields it does return
3. Schema consistency: 0 missing fields across 1,000 items

Speed

Usability

DataForSEO's model is task_post → task_get. One call creates and launches the task, a second one fetches the results when they're ready.

https://api.dataforseo.com/v3/business_data/trustpilot/reviews

1. Create the task

curl --request POST \
  --url "https://api.dataforseo.com/v3/business_data/trustpilot/reviews/task_post" \
  --user "$DATAFORSEO_LOGIN:$DATAFORSEO_PASSWORD" \
  --header "Content-Type: application/json" \
  --data '[
    {
      "domain": "www.thepearlsource.com",
      "depth": 200,
      "sort_by": "recency",
      "priority": 1
    }
  ]'
f

Response:

{
  "version": "0.1.20260717",
  "status_code": 20000,
  "status_message": "Ok.",
  "cost": 0.0075,
  "tasks_count": 1,
  "tasks_error": 0,
  "tasks": [
    {
      "id": "07211450-2117-0358-0000-be4f52a532ca",
      "status_code": 20100,
      "status_message": "Task Created.",
      "cost": 0.0075,
      "result_count": 0,
      "result": null
    }
  ]
}
f

2. Poll for completion

curl --request GET \
  --url "https://api.dataforseo.com/v3/business_data/trustpilot/reviews/task_get/07211450-2117-0358-0000-be4f52a532ca" \
  --user "$DATAFORSEO_LOGIN:$DATAFORSEO_PASSWORD"
f

3. Retrieve results

{
  "status_code": 20000,
  "status_message": "Ok.",
  "tasks": [
    {
      "id": "07211450-2117-0358-0000-be4f52a532ca",
      "status_code": 20000,
      "status_message": "Ok.",
      "cost": 0,
      "result_count": 1,
      "result": [
        {
          "domain": "www.thepearlsource.com",
          "reviews_count": 17558,
          "rating": {
            "rating_type": "Max5",
            "value": 4.8,
            "votes_count": null,
            "rating_max": 5
          },
          "items_count": 200,
          "items": [ /* 200 review objects */ ]
        }
      ]
    }
  ]
}
f

Each task takes one domain, but you can submit up to 100 tasks in a single task_post request, and DataForSEO ships an official MCP server for Claude, Cursor or ChatGPT workflows.

Verdict

DataForSEO is the pick when cost and simplicity matter more than depth. At $0.038 per 1K it's the cheapest API here by a wide margin, and the workflow is two calls. But 200 reviews per business is a hard ceiling, so it's a sampling tool, not a collection tool.

Also tested: Outscraper and OpenWeb Ninja

Both made the shortlist. Neither made the recommendations.

Outscraper

Outscraper was reliable: 1,000/1,000 reviews, 0 errors, 12/13 ground-truth fields, 20/20 matched, and it accepts up to 1,000 domains in one call, the widest batch input of the five.

OpenWeb Ninja

OpenWeb Ninja has the broadest SDK coverage of the five (Shell, Ruby, Node.js, PHP, Python) and its first run returned 1,000/1,000.

An API that works once and then rate-limits you into nothing isn't one I can recommend.

Which Trustpilot reviews API should you pick?

lobstr.io: every review, every business

Apify via memo23: depth, if you already live on Apify

Same 5,000/5,000 result, faster in a single run, $0.63 to $0.66 per 1K measured. Worth it if your pipeline already runs on Apify Actors. Not worth adopting Apify for.

DataForSEO: cheap samples

$0.038 per 1K and a two-call workflow. If 200 reviews per business tells you what you need to know, nothing else comes close on price.

FAQ

Why do most Trustpilot APIs stop at 200 reviews?

Is scraping Trustpilot reviews legal?

Is the Trustpilot API free?

No. For your own reviews, Trustpilot's Free, Starter and Plus business plans don't include API access; Premium and Enterprise can add the API Module as a paid add-on, priced on request. For other businesses' reviews, the Data Solutions API sits behind a waitlist with no published pricing.

Why isn't Outscraper recommended?

Cost. It delivered 1,000/1,000 with zero errors and excellent docs, but at $2.70 to $3.00 per 1K it's the most expensive API I tested, and it's capped at 200 reviews per business like DataForSEO, which does the same job for $0.038.

Can I reproduce these results?

Conclusion

I tested 5 Trustpilot reviews APIs under the same conditions. Two got past 200 reviews per business: lobstr.io and Apify's memo23 Actor.

lobstr.io is my recommendation for a Trustpilot reviews API. It's purpose-built for this, it returned every review I asked for with the widest schema and a perfect ground-truth match, and it did it on a $20 plan with no tier surprises.