Source connector

Trustpilot connector

Trustpilot integration for databases, warehouses and BI tools

Consumer reviews and business reputation data. Datrise captures Trustpilot entities such as reviews, business units, consumers, star ratings, replies and invitations, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Trustpilot Business API (Service Reviews API / Business Units API) authenticates with OAuth 2.0, API key, incremental runs key on updatedAt, and Trustpilot caps calls at Trustpilot recommends staying under 833 calls per 5 minutes and 10,000 calls per hour.

Of the 6 objects, 6 sync as upserts keyed on the primary key and 0 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `trustpilot_reviews`) with a schema derived from the Trustpilot API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Trustpilot pipeline page, and join the waitlist to get the Trustpilot connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Trustpilot data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
reviews	trustpilot_reviews	Upsert by primary key, incremental on updated-at
business units	trustpilot_business_units	Upsert by primary key, incremental on updated-at
consumers	trustpilot_consumers	Upsert by primary key, incremental on updated-at
star ratings	trustpilot_star_ratings	Upsert by primary key, incremental on updated-at
replies	trustpilot_replies	Upsert by primary key, incremental on updated-at
invitations	trustpilot_invitations	Upsert by primary key, incremental on updated-at

Trustpilot API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Trustpilot Business API (Service Reviews API / Business Units API)
Authentication	OAuth 2.0, API key — Authenticated business endpoints (e.g. `/v1/private/...`) require OAuth 2.0 (Authorization Code, Implicit, or Client Credentials; the Password grant is deprecated), while public read-only endpoints accept a simple API key.
Pagination	token — List endpoints return up to 100 results per page and hand back a `nextToken`/`cursor`/`pageToken` value (naming varies by endpoint) to fetch the next page.
Rate limit	Trustpilot recommends staying under 833 calls per 5 minutes and 10,000 calls per hour
Incremental cursor	updatedAt — Reviews carry both `createdAt` and `updatedAt` timestamps, but there is no documented `updatedSince` query filter, so a connector must page through and compare `updatedAt` client-side, or rely on webhooks for near-real-time change capture.
Webhooks	Yes — Private webhooks API (`review.created`, `review.replied`, registered via `/v1/private/webhooks`)
Bulk export	No
Deletes detectable	No

Official API reference

What bites when replicating Trustpilot

There is no full bulk-export endpoint; the Data Solutions/Reviews APIs are query-first (by Business Unit ID, domain, or date range), so a from-scratch historical backfill means iterating known business units rather than one export call.
Trustpilot's rate-limit numbers (833 calls/5 min, 10K calls/hour) are stated as recommendations, not hard technical caps, and Trustpilot explicitly recommends webhooks over polling to stay under them.
Deleted or moderated reviews are not exposed through a deleted-records feed; a connector polling `updatedAt` on `/v1/reviews/{reviewId}` can miss removals entirely and must treat a 404 on re-fetch as the deletion signal.
The `password` OAuth grant is deprecated, so new integrations must use Authorization Code, Implicit, or Client Credentials, and code samples referencing the password grant will fail for new API clients.

Compare this against every other documented API

Popular destinations for Trustpilot

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Trustpilot connector FAQ

What Trustpilot data does the connector extract?: 6 objects: reviews, business units, consumers, star ratings, replies and invitations. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
Is the Trustpilot integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Trustpilot data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Trustpilot → destination pair has its own page with the object-to-table mapping.

Related sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Trustpilot pipeline with guided onboarding

Join the waitlist to get priority access for Trustpilot integrations with guided setup, schema-aware mapping, and production-grade incremental sync.