# Trustpilot Scraper in Python: Reviews, Star Filters and the Page-10 Login Wall > Source: https://scrape.do/blog/trustpilot-scraping/ Published: 2026-11-16 · Updated: 2026-11-16 · Authors: Serhat Kurtulus · Categories: Scraping Use Cases A Trustpilot scraper has three things to get past: a 403 from AWS WAF on the very first request, a review list that shows English reviews only unless you ask for more, and a login wall that turns page 11 into a sign-in page with a 200 status. This guide builds four Python scrapers through Scrape.do: company profiles, reviews page by page, reviews sliced by star rating, and category listings. All four read the JSON that Trustpilot embeds in every page, so none of them depends on CSS class names. ## Why Trustpilot Scraping Starts with a 403 A plain `requests.get()` to `https://www.trustpilot.com/review/www.amazon.com` gets no reviews back. It gets a 403 and a 266-byte JSON body that calls the script a bot: ```json {"error":true,"message":"Your request has been blocked as it has been identified as coming from a bot that's against our terms of service. If you believe this is an error, please contact support via https://help.trustpilot.com/s/contact-us and supply full details."} ``` The site works fine in a browser. Our constraint is the raw HTTP response, and it depends on who Trustpilot thinks is asking. ### Two Blocks from the Same AWS WAF A Chrome user agent with browser `Accept` headers does not help. On November 5, 2026 it got the same 266-byte JSON, with `Server: CloudFront` and `X-Cache: Error from cloudfront` in the response headers. In our September R&D the same disguise drew a different 403: a 991-byte "Verifying your connection..." page that loads `challenge.js` from an `awswaf.com` host. That is AWS WAF in front of CloudFront, and between the two runs a user agent string alone stopped earning even the challenge. Some guides blame Cloudflare for this block; the headers say otherwise. ![Trustpilot's AWS WAF interstitial reading Verifying your connection, served as a 403 before the challenge script runs](/uploads/blog/trustpilot-scraping/trustpilot-scraping-aws-waf-challenge-page.png) A real Chrome engine solves that challenge in a few seconds (2 to 4 in our September test), which is why Selenium and Playwright scripts get through at low volume. `requests` cannot execute `challenge.js`, so for an HTTP client the interstitial is the end of the road. More on reading that kind of response in our guide to [fixing Python requests 403 errors](/blog/python-requests-403-forbidden/). ### Getting Past the Block with One Plain Scrape.do Call The same URL routed through [Scrape.do](https://scrape.do) returns 200 with the full page. No `super=true`, no `render=true`, no `geoCode`: each request we send carries the token and the target URL and nothing else. Every Trustpilot call costs 10 credits. That number comes from the `Scrape.do-Request-Cost` response header, which read 10 on every request we logged on November 5, 2026. The per-domain table in the [request costs docs](/documentation/request-costs/) does not list trustpilot.com, so the header is the source to trust. In our September R&D, `super=true` and `render=true` returned the same page at the same 10 credits, so there is nothing to gain from either. The page is server-rendered, so none of the [JavaScript rendering techniques](/blog/how-to-scrape-javascript-rendered-web-pages-with-python/) are needed here. Two failure modes are worth planning for. In September, 3 of about 250 calls came back as `502 ROTATION_FAILED`, which the error body describes as transient and which is not billed. We saw no 502 in about 180 calls on November 5, but one call came back as a 200 with an empty body, which crashed the first version of the star-slice script. Every fetch helper below retries once when either happens; a full backoff setup is in our guide to [retrying Python requests](/blog/python-requests-retry/), but one retry was enough on this site. Trustpilot's [Terms of Use for consumers](https://corporate.trustpilot.com/legal/for-reviewers/terms-of-use-for-consumers) (version 8.0, in force since October 1, 2026) forbid "text mining, data mining or web scraping of our platform for any purpose without our express permission", and its [robots.txt](/blog/robots-txt/) ends with a blanket `Disallow: /`. We stay on public pages, keep the volume modest, never log in, and never open reviewer profile pages. The longer [web scraping legality](/blog/web-scraping-legality/) discussion and the FAQ below pick this up. ## What the Official Trustpilot API Covers Trustpilot does have an API, whatever some tutorials claim. The documentation at developers.trustpilot.com lists public endpoints for business units and their reviews, authenticated with an API key, and private endpoints that need a business user's OAuth token. ### Trustpilot API Pricing and Who Gets a Key Access is the hard part. On Trustpilot's [business pricing page](https://business.trustpilot.com/pricing), API access is listed as an add-on, not as part of the free plan. The paid plans it sits on start at $319 a month for Plus and $799 a month for Premium, per domain and billed annually, with Enterprise priced on request. No price for the API add-on itself is published. The [rate-limiting page](https://developers.trustpilot.com/rate-limiting/) recommends staying under 833 calls per 5 minutes or 10,000 per hour. The bigger limit is scope. The business API is built for a company working with its own reviews. For other companies' reviews, Trustpilot runs a separate product called Data Solutions, with a Display API (business details and up to five latest reviews per business) and an Insights API (full reviews and categories). [Getting started](https://developers.trustpilot.com/data-solutions-get-started/) means joining a waitlist, and no pricing is published. ## Scraping a Trustpilot Company Profile: TrustScore, Star Distribution and Reply Rate The profile is the simplest page type and the one where Trustpilot's data source shows itself first. ### Prerequisites We need Python 3, `requests` and `beautifulsoup4` (`pip install requests beautifulsoup4`), and a Scrape.do token. `json`, `csv` and `urllib.parse` ship with Python. At 10 credits per call, the 1,000 free credits on signup cover 100 Trustpilot pages. The [Python web scraping guide](/blog/python-web-scraping/) covers `requests` and BeautifulSoup from the ground up. ### Where the Data Lives: the Page's Own JSON Trustpilot is a Next.js site, and every server-rendered page carries its complete state inside one tag: `