Trustpilot reviews API get reviews by domain

Trustpilot doesn't offer a simple, open API for pulling any business's reviews — its own APIs are built primarily for businesses managing their own Trustpilot profile, not for reading a competitor's or aggregating reviews across many domains at once.

Roketfy's Trustpilot reviews API is built for that broader use: pass a business domain and it returns rating, review title, text, reviewer name and any company reply as structured JSON, for any business listed on Trustpilot.

Trustpilot addresses each business's review page by the domain it's registered under — for example, www.example.com in trustpilot.com/review/www.example.com — which doesn't always match the company's marketing name exactly. Rather than guessing, run the search endpoint first with the company name or business category as the keyword.

The search endpoint returns matching businesses along with the exact domain each one's review page uses, so you can confirm you've got the right business before spending credits on its full review set — especially useful for companies with several regional or product-line variants on Trustpilot.

The depth parameter controls how many reviews come back per call, from 1 up to 200, defaulting to 20. Billing on the reviews endpoint is per 20 reviews at 10 credits, so a deeper pull scales proportionally rather than costing a flat rate regardless of size.

Business search is billed per 10 results at 19 credits, with depth going up to 140 — worth running sparingly, since in most workflows you only need it once per business to resolve its domain, not on every review pull.

Yes. sort_by accepts recency for the newest reviews first, or relevance (the default) for Trustpilot's own ranking. For ongoing monitoring, recency is generally the better choice — it lets you pull only what's changed since your last check rather than re-fetching Trustpilot's idea of the most relevant reviews every time.

For a SaaS company, Trustpilot reviews often surface billing confusion, onboarding friction and feature requests days before the same feedback reaches a support queue through official channels — pulling reviews on a schedule and routing anything that reads like a support issue to the right team closes that gap. For e-commerce, reviews tend to cluster around shipping speed, product quality and return experience, which makes Trustpilot data a useful cross-check against a store's own on-site reviews.

In both cases, the value compounds once reviews are pulled consistently rather than checked ad hoc: a rating that's been drifting for weeks is a very different signal than a rating that dipped once and recovered, and only a running pull can tell the two apart.

Yes — resolve a competitor's domain once with the search endpoint, then pull their reviews on the same schedule you pull your own. Tracking review volume and rating trend for a handful of competitors alongside your own numbers turns a one-off benchmark into an ongoing comparison, which is far more useful for spotting a shift in the market than checking Trustpilot pages by hand once a quarter.