Trustpilot API: pricing, API key, documentation and integration limits
The Trustpilot API is real, well documented and gated. Trustpilot's own developer portal states that you must have a Trustpilot for Business account with access to the API module, and on the public plans page API access is listed as an add-on on Plus, Premium and Enterprise. It is not listed on Free or Starter at all. Since Plus starts at $319 per month per domain on a 12-month commitment, that is the real floor before the add-on is even quoted. Below is the endpoint map, the public and private split, the documented limits, and how to tell whether you need the API or just a widget.
No API key required
Sources
Layout
Brand color
Minimum rating
No reviews match those filters
Turn a source back on or lower the minimum rating.
·
reviews shown
from Google · G2 · direct
Drops next to any CTA: signup, pricing, checkout.
Paste this once, anywhere in your HTML. The widget inherits your settings from the studio and stays in sync when you change them.
Create your account to activate your embed code.
Automated request email
From: Your Company <[email protected]>
Subject: Quick favor? It takes 40 seconds
Hi Jordan,
You've been with us for 3 months, thanks for that. Would you share how it's going? One click below, 40 seconds, done.
Sent automatically 90 days after signup · timed to the customer's timezone
See it land in your own inbox
We'll send you this exact sequence the way your customers would receive it.
Most people searching for the Trustpilot API only want reviews on their own pages. That is a script tag, not a $319 a month integration project.
The question behind most Trustpilot API searches
Which Trustpilot plans include API access?
None of them include it outright. On the plans page, API access is an add-on line item, and it only appears from Plus upward. This is the detail that decides whether an integration is worth scoping, and almost nobody publishes it plainly.
| Plan | Published price | Invitations per month | API access |
|---|---|---|---|
| Free | $0 | 50 | Not listed |
| Starter | From $99 per month, per domain, billed annually | 100 | Not listed |
| Plus | From $319 per month, per domain, billed annually | 300 | Add-on |
| Premium | From $799 per month, per domain, billed annually | 1,000 | Add-on |
| Enterprise | Contact sales for a pricing estimate | Unlimited | Add-on |
Read at business.trustpilot.com/plans on 15 August 2026. Prices are Trustpilot's published figures, quoted as written. Trustpilot states that all contracts are a 12-month commitment, prepaid, and that Starter is "available only to new small business customers (up to $5M revenue)", so a company above that line cannot buy the $99 entry point at all.
The add-on has no published price
Trustpilot lists API access as an add-on on three plans and never says what the add-on costs. You will get that number from a sales conversation, priced against your account. Budget the plan, then treat the API line as an unknown.
Even Enterprise does not include it
This is the part that surprises people. Buyers often assume the top tier bundles everything. On the published table, Enterprise carries the same add-on marker as Plus and Premium, alongside a separate add-on for the Salesforce integration.
Pricing is per domain, not per company
Every published price is per domain. Two brands means two subscriptions before anyone talks about API keys, which is what makes multi-brand Trustpilot integrations expensive in a way the plan table does not make obvious at first glance.
The endpoint map
What the Trustpilot API actually covers
Trustpilot does not ship one reviews API. It ships a set of APIs grouped under Trustpilot for Business, plus a newer Data Solutions product for querying the wider database. Knowing which one owns your use case saves a week of reading.
| API | What it does | Typical reason to use it |
|---|---|---|
| Business Units API | Look up a company profile and read its reviews, TrustScore and public boxes | Pulling your own review history into a database |
| Service Reviews API | Read individual reviews, post and delete replies, tag reviews, raise Find Reviewer requests | Replying to reviews from a helpdesk instead of the Trustpilot UI |
| Product Reviews and Private Products API | Manage product catalogues and the reviews attached to individual SKUs | Ecommerce sites showing star ratings on product pages |
| Invitations API | Trigger review invitations programmatically | Firing a review request when an order is marked delivered |
| Consumer and Consumer Profile API | Access consumer data and profiles | Matching a reviewer back to an account |
| Categories and Resources API | Business category data and general resource lookups | Classifying business units in a directory build |
| Business Signup API | Creates business accounts programmatically | Platforms onboarding merchants onto Trustpilot |
| Data Solutions API | Fuzzy search across business units, TrustScore and review statistics, latest reviews, categories | Market research and competitor benchmarking across many companies |
| Deletions API | Data removal management | Honouring deletion requests in your own copy of the data |
Product names and descriptions as published on Trustpilot's developer portal, read 15 August 2026. Data Solutions is flagged as a new offering and is the one to look at if you want data about businesses other than your own.
The split that trips people up
Public API key versus private OAuth
Trustpilot runs two access levels, and the boundary between them is not where most developers assume. An API key gets you a surprising amount of public data. Everything commercially useful sits behind OAuth.
| Public APIs | Private APIs | |
|---|---|---|
| Credential | API key, which Trustpilot calls your Client ID | OAuth 2.0 access token for a business user |
| How it is sent | As an apikey HTTP header |
As a bearer token obtained through a grant flow |
| Grant types | Not applicable | Authorization Code, Implicit, Client Credentials, Password (deprecated) |
| Token lifetime | Key does not expire on a schedule | Access token 100 hours, refresh token 30 days |
| Review data returned | What is already visible on the public profile | Adds customer email and order ID |
| Can post replies | No | Yes |
| Whose business units | Any business unit on Trustpilot | Only the ones your account owns |
Two documented gotchas worth knowing before you scope
Trustpilot warns that you "should avoid passing your API key as a query parameter, as this can expose your API key", so the header is the only sensible route. More consequentially for enterprise security teams, the docs state plainly that "OAuth authentication doesn't support multi-factor authentication". If your Trustpilot logins are behind MFA by policy, that is a conversation to have with security before the build, not after.
Do not regenerate tokens per call
Access tokens last 100 hours and are meant to be reused. Trustpilot's guidance is direct about it: wait until the current token expires before requesting a new one, because refreshing too often gets requests rejected with HTTP 429. Teams that wrap every call in a fresh token exchange hit that wall on day one and misread it as a rate limit on the data endpoints.
The endpoints that matter
How to get reviews out of Trustpilot
Most integrations only ever touch three or four endpoints. These are the ones that carry review data, with the ceilings Trustpilot documents for each.
| Endpoint | Access | What it returns |
|---|---|---|
| GET /v1/business-units/{id}/reviews | API key | Your public reviews, filterable by stars, language, tag and whether you responded. Limited to 100,000 records. |
| GET /v1/business-units/{id}/all-reviews | API key | The same data past the 100,000 ceiling, paged with a pageToken cursor rather than page numbers. |
| GET /v1/private/business-units/{id}/reviews | OAuth | The same reviews plus customer email and order ID, with date range, source and reference ID filters. |
| GET /v1/business-units/find?name={domain} | API key | Public information for a business unit, looked up by domain name. This is how you resolve a business unit ID. |
| GET /v1/business-units/all | API key | All business units, including domains with no reviews. 1,000 results per page by default, navigated with a cursor. |
| GET /v1/reviews/latest | API key | The latest reviews written in a specific language. |
| POST /v1/private/reviews/{id}/reply | OAuth | Publishes a reply. The matching DELETE removes it. |
| POST /v1/private/reviews/{id}/find-reviewer | OAuth | Raises a Find Reviewer request when a review cannot be matched to a known customer. |
What a Trustpilot review object contains
A service review carries id, stars, title, text, language, createdAt, updatedAt, numberOfLikes, isVerified, companyReply, consumer, location, businessUnit, links and invitation data. That last field is the one worth planning around: because Trustpilot owns the invitation, you can trace a review back to the send that produced it, which is something the Google APIs cannot do at all.
The 100,000 record ceiling in practice
Almost no business hits it. A company collecting 500 reviews a month takes over 16 years to reach 100,000. It matters if you are building a research product across many business units, and that is precisely the case Trustpilot points at the Data Solutions API and its cursor-based all-reviews endpoint instead.
Documented limits
Trustpilot API rate limits and the rules around caching
Trustpilot publishes guidance rather than a hard contractual quota, and the numbers are generous for a normal review workflow. The architecture rules matter more than the ceilings.
833
calls per 5 minutes
The shorter window Trustpilot asks you to stay under. It works out to roughly 2.8 calls a second, so it is a burst limit more than a throughput limit.
10,000
calls per hour
The hourly guidance. A nightly sync of even a large review history sits nowhere near it. Frontend polling blows through it quickly.
1
request per second
Trustpilot also asks that you not exceed about one request per second sustained. Build the backoff in from the start rather than after the first incident.
429
the code you will see
Returned when you refresh an OAuth access token too often. It reads like a data rate limit and is not one, which sends people debugging in the wrong direction.
Trustpilot's own three rules, and why the third one matters most
The published best practices are short. First, use webhooks: "avoid pulling data if you can use webhooks instead", so you are pushed a review when it arrives rather than polling for it. Second, reuse your authentication token instead of generating one per call. Third, and this is the one that quietly changes your architecture, store and update review data in your own backend, because Trustpilot explicitly says to "avoid pulling your review data directly into your website's frontend", since the page then calls the API on every single view.
That third rule is a clear statement that the API is not the intended way to put reviews on a web page. If your only goal is a rating and a few quotes rendering on your homepage, the API is the expensive path to a job a widget already does, and Trustpilot's own documentation is telling you so.
Cross platform reality check
Trustpilot API compared with the Google review APIs
Teams that need reviews from more than one source usually discover the platforms are wildly inconsistent. Trustpilot is generous with depth and strict about money. Google is the reverse.
| Trustpilot API | Google Places API | Google Business Profile API | |
|---|---|---|---|
| Reviews returned | Up to 100,000, more via cursor | Maximum of 5, no pagination | All of yours |
| Other companies' reviews | Yes, public data, and broadly via Data Solutions | Yes, but only 5 | No |
| Cost to reach it | Plus from $319 per month plus an unpriced add-on | Billed per call on Google's most expensive Places SKU | No per-call charge once approved |
| Approval needed | Commercial, via the API module on your plan | No, just billing enabled | Yes, a manual application |
| Can post replies | Yes | No | Yes |
| Can trigger review requests | Yes, Invitations API | No | No |
| Customer identity in the payload | Email and order ID on the private endpoint | None | None |
The headline difference is customer identity. Trustpilot's private endpoint hands back the email address and order ID behind a review, so you can join review data to revenue. Neither Google API does, which is why the same dashboard built on both sources ends up with a rich Trustpilot table and a thin Google one. The full breakdown of the two Google review APIs is here, including the five review cap and the approval quota check.
Before you scope the build
Do you actually need the Trustpilot API?
A large share of Trustpilot API searches come from someone who has been asked to put reviews on a website. That job does not need an API, a key, an add-on or a $319 a month plan. Here is the honest split.
| What you are trying to do | Right tool |
|---|---|
| Show reviews and a rating on your website | A widget. Trustpilot's own guidance says not to call the API from your frontend, and a TrustBox or a third party widget handles caching, refresh and layout for you. |
| Show reviews from Trustpilot and Google together | An aggregator that already holds connections to both, rather than two separate integration projects with two different approval processes. |
| Get review data into a warehouse or BI tool | The API, or a scheduled CSV export. This is a genuine API use case, and the one worth paying for. |
| Alert a Slack channel when a 1 star review lands | Webhooks, or monitoring software that already does it. Polling for this is what the rate limit guidance is written to prevent. |
| Send review invitations after an order | The Invitations API, or a review platform with an ecommerce integration that fires the same sequence with no code. |
| Benchmark competitors' TrustScores | Data Solutions, the public business unit lookups, or a monitoring tool that watches the profiles for you. |
Where ReviewJet fits
If the reviews are meant for a page, skip the integration
ReviewJet is not a replacement for the Trustpilot API and does not pretend to be. If you need review rows in Snowflake with order IDs attached, buy the add-on and build it properly. What we replace is the far more common version of this project: someone needs Trustpilot, Google and G2 reviews rendering on a website, and the quoted path to that is a plan upgrade plus an integration sprint.
Our widget is a script tag. It collects new reviews with request sequences, pulls your existing ones into one feed, and displays them without a key, a quota or a per-domain multiplier. Pricing is flat and published: $24 a month billed yearly on Starter, with CSV export and API access on the Pro plan for teams that do need the data elsewhere.
No key, no quota
A script tag renders the widget. There is no API key to rotate and no hourly call ceiling to design around.
Flat, not per domain
One account covers your brands. Trustpilot prices every published plan per domain, which is where multi-brand budgets break.
Four sources, one feed
Google, G2, Trustpilot and reviews you collect yourself, displayed together instead of in four separate embeds.
Export when you need it
CSV export and API access sit on the Pro plan, so the data path exists without starting there.
Questions people actually search
Trustpilot API questions, answered
Keep reading
Related Trustpilot and review data pages
Trustpilot pricing
The full published rate card, the 12-month commitment, and the $5M revenue rule that blocks most companies from the $99 tier.
Trustpilot widget
The display route, including which two TrustBoxes the free plan gives you and why neither shows review text.
Google Reviews API
The five review cap on Places, the Business Profile approval process, and the quota trick that tells you if you are approved.
Export reviews to Google Sheets and BI tools
Getting Trustpilot, Google and G2 review data into a spreadsheet, Power BI or BigQuery without a native connector.
Trustpilot alternatives
What the rest of the category charges, and which platforms publish a price at all.
Reviews aggregator
One feed across Google, G2 and Trustpilot instead of three integrations with three approval processes.
Reviews on your site without an API add-on
Google, G2, Trustpilot and direct reviews in one widget, with collection sequences that grow the number you have. Flat pricing from $24 a month, no per domain multiplier.
From $24/mo, billed yearly. No per-review fees.