Business search
1 credit/v1/trustpilot/business-searchSearch Trustpilot businesses by name or keyword. Returns domains and review counts. Matches companies, not products. First calls can take ~15-45s. Standard tier (1 credit).
query, depth
Trustpilot APIGet Trustpilot business review data with one API
Fetch Trustpilot business search and company reviews as structured JSON with one SocialCrawl API key. Shared review schema. Reads are priced in credits.
/v1/trustpilot
2 active endpoints. Search then reviews.
- GET /v1/trustpilot/business-search
- GET /v1/trustpilot/reviews
What Trustpilot endpoints does SocialCrawl ship?
Two live read endpoints for Trustpilot. Find a company domain, then pull reputation reviews. Company reviews only. Not product SKU reviews.
Business reviews
5 credits/v1/trustpilot/reviewsCustomer reviews for a business domain from search. Stars, text, verified flags, owner responses. Company reputation, not product SKUs. Advanced tier (5 credits).
domain, depth, sort
Trustpilot API2 endpoints supported
View docsReturns Trustpilot businesses matching a keyword: company name, its Trustpilot domain, its own website, its review page URL, and total review count.
Use it to find a company's Trustpilot domain, which the reviews endpoint needs. It matches businesses, not products.
1 credit
GET/v1/trustpilot/business-search?query=nike&depth=20
query · Business name or keyword (e.g. 'nike'). Matches companies, not products; do not pass a bare domain.
$ curl https://www.socialcrawl.dev/v1/trustpilot/business-search?query=nike&depth=20 \
-H "x-api-key: sc_YOUR_API_KEY"idle
// Running this live needs your own API key. Hit "Try it" to see an example responseHow the Trustpilot API works
Trustpilot is a normal SocialCrawl data surface. You call GET /v1/trustpilot/… with an API key, spend credits on live misses, and get a single JSON envelope back.
Authenticate every call
Send your key in the x-api-key header. No Trustpilot OAuth app for public reads. The same key works across SocialCrawl platforms.
GET with query params
All Trustpilot routes are GET. Pass query, domain, depth, sort as query strings. We validate formats before charging.
Pay in credits, not seats
business-search costs 1 credit. reviews costs 5 credits. A cold task can take 15-45s, then cache.
Read one JSON envelope
Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached. Lists also carry pagination when the route pages.
The usual integration chain
Most products discover entities first, then deepen detail and reviews only when needed.
01Find business
GET /v1/trustpilot/business-search?query=…AuthorList of businesses with domain ids
Reviews require a Trustpilot domain, not a product ASIN.
02Reviews
GET /v1/trustpilot/reviews?domain=…ReviewList for the company domain
Brand reputation text for VoC.
03Sort
GET /v1/trustpilot/reviews?domain=…&sort=relevanceSame ReviewList ordered by relevance or recency
Pick recency for monitoring, relevance for research.
04Depth
GET /v1/trustpilot/reviews?domain=…&depth=100Larger review window up to platform max
Depth controls rows in one call; no infinite cursor.
request
GET /v1/trustpilot/business-search?query=nike&depth=20
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here
GET /v1/trustpilot/reviews?domain=www.nike.com&depth=20&sort=recencyresponse envelope
{
"success": true,
"data": {
"items": [
{
"author": {
"id": "www.nike.com",
"username": "www.nike.com",
"display_name": "Nike",
"posts_count": 12000,
"url": "https://www.trustpilot.com/review/www.nike.com"
}
}
]
},
"credits_used": 1,
"credits_remaining": 9999,
"request_id": "req_…",
"cached": false
}What lands in data
Field names match the rest of SocialCrawl where archetypes align. Parse once, reuse across platforms.
AuthorListbusiness-search
business display name, domain id, review count, Trustpilot url
ReviewListreviews
items[] with rating, text, verified, responses[], published_at
Review windowreviews + depth
depth-capped single page, max 200
404 refundempty business
no reviews domain returns 404 and refunds
Inside the gateway
Same request lifecycle as every other /v1 platform endpoint. Trustpilot is not a sidecar.
- 01
Edge receives the call
Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit (600/min) and concurrency (50 in flight per key).
- 02
Validate, then debit
Registry lookup finds trustpilot/business-search (or reviews). Required params and format checks run first. Invalid input returns 400 with no charge. Valid calls debit the tier cost atomically before upstream work.
- 03
Cache or fetch
A deterministic cache key is built from platform + resource + params. Hit: return immediately, credits_used = 0. Miss: Trustpilot tasks are spin-polled server-side. Retries on 5xx/network with a circuit breaker if the source is unhealthy.
- 04
Normalize and return
Upstream JSON is mapped to commerce archetypes (Product, ProductList, ReviewList, SellerList, App, PlaceList as applicable), validated against the canonical Zod schema, then wrapped in the success envelope and logged for billing audit.
Billing rules that matter in production
- business-search: 1 credit
- reviews: 5 credits
- Cache hit: 0 credits
- Empty / hard fail: auto-refund
- Bad params: 400, never charged
- No credits: 402, never charged
- Cold calls often 15-45s
- depth caps review window (max 200)
- No write or reply-as-business tools
How we get the data
Trustpilot is public read data. We normalize it into the SocialCrawl schema so your code does not learn a second vendor SDK.
What Trustpilot is for this API
Public company profiles and customer reviews about the business. Not product pages.
How SocialCrawl reaches it
Business profile and review reads run as server-side tasks. The async lifecycle stays server-side.
What leaves our edge
AuthorList for businesses and ReviewList for domain reviews.
What we do not ship live
No invite-to-review, reply-as-business, or private analytics.
field map sketch
Trustpilot company→ author.*domain as id/username
review body→ ReviewList items[]stars, text, owner responses
depth / sort→ query controlsno cursor beyond depth max
What this API is used for
The jobs this API is most often used for.
2active Trustpilot endpoints in the registry
1 / 5credit ladder for business-search vs reviews
Brand reputation and support-quality monitoring
Callers concentrate on search or taxonomy, then deepen detail and reviews for shortlisted entities. Company-level Trustpilot reviews by domain with a flat 5-credit pull after 1-credit search. No Trustpilot partner OAuth.
Live misses are typically a few seconds. Some routes can take longer on cold cache.
What people build with the Trustpilot API
The jobs Trustpilot data is most often used for. Each one is a full recipe with the endpoint chain and pricing.
Use case examples
Common ways teams put this data to work, and the stack each one tends to run.
Brand ops
Python, Slackbusiness-search for domains, reviews for recency monitoring.
VoC research
Node, notebooksreviews by domain with depth for language mining.
Competitive intel
BI loadssearch peer brands, sample review volume and tone.
Call it in two lines
Search is 1 credit. Reviews are 5. Cache hits are free.
curl "https://www.socialcrawl.dev/v1/trustpilot/business-search?query=nike&depth=20" \
-H "x-api-key: sc_your_api_key_here"curl "https://www.socialcrawl.dev/v1/trustpilot/reviews?domain=www.nike.com&depth=20&sort=recency" \
-H "x-api-key: sc_your_api_key_here"Same key as the rest of the catalog
Endpoints
What data does the Trustpilot API return?
Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.
Comparison
How does SocialCrawl compare to DIY scraping for Trustpilot data?
Same Trustpilot data, two very different paths. Auth, rate limits, schema, and cost, side by side.
| Feature | SocialCrawl | DIY scraping |
|---|---|---|
| Authentication | One x-api-key, sign up and call | None, but you manage proxies and anti-bot evasion yourself |
| Setup | Two GET requests: business-search, then reviews | Headless browser, proxy pool, HTML parsers, and retry logic to build |
| Response schema | Unified ReviewList JSON shared with 64 other platforms | Raw HTML you parse. Selectors break when Trustpilot redesigns |
| Pricing | 1 credit per search, 5 per review pull; 100 free credits, no card | Proxy and compute costs plus ongoing engineering time |
| Data coverage | Star ratings, full text, verified flags, language, and owner replies, up to 200 reviews per call | Whatever your parser extracts before the markup changes |
| Maintenance | Upstream changes absorbed by SocialCrawl | You fix the scraper every time the page structure shifts |
Authentication
SocialCrawl
One x-api-key, sign up and call
DIY scraping
None, but you manage proxies and anti-bot evasion yourself
Setup
SocialCrawl
Two GET requests: business-search, then reviews
DIY scraping
Headless browser, proxy pool, HTML parsers, and retry logic to build
Response schema
SocialCrawl
Unified ReviewList JSON shared with 64 other platforms
DIY scraping
Raw HTML you parse. Selectors break when Trustpilot redesigns
Pricing
SocialCrawl
1 credit per search, 5 per review pull; 100 free credits, no card
DIY scraping
Proxy and compute costs plus ongoing engineering time
Data coverage
SocialCrawl
Star ratings, full text, verified flags, language, and owner replies, up to 200 reviews per call
DIY scraping
Whatever your parser extracts before the markup changes
Maintenance
SocialCrawl
Upstream changes absorbed by SocialCrawl
DIY scraping
You fix the scraper every time the page structure shifts
FAQ
Have a question? We got answers
Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.
Contact usHow do I scrape Trustpilot reviews with an API?
SocialCrawl provides 2 Trustpilot endpoints. Call GET /v1/trustpilot/business-search to find a company and its Trustpilot domain, then GET /v1/trustpilot/reviews with that domain to receive star ratings, review text, verified status, and owner replies as unified JSON.
Does the Trustpilot API return product reviews?
No. Trustpilot reviews are about the company itself (shipping, refunds, and support sentiment) keyed by business domain, never a specific product. For product reviews, use SocialCrawl's Google Shopping or Amazon review endpoints instead.
What data does the SocialCrawl Trustpilot API return?
Business search returns each company's name, Trustpilot domain, website, and total review count. Reviews returns per-review star rating, title, full text, verified flag, language, reviewer profile, owner/brand responses, and publish date, all in one unified schema.
How much does the Trustpilot API cost?
Business search costs 1 credit (standard tier) and reviews cost 5 credits (advanced tier) per request. New accounts get 100 free credits with no credit card required, so you can test both endpoints before paying anything.
Is scraping Trustpilot reviews legal?
SocialCrawl reads only publicly available Trustpilot review pages, the same content anyone can see by visiting the URL. You are responsible for ensuring your use case complies with Trustpilot's terms of service and applicable data protection laws. SocialCrawl operates under a documented GDPR legitimate-interest framework: public, logged-out data only, no credential use, short-lived caches (2 to 30 minutes) with no persistent store, and a public opt-out channel for anyone whose public info appears in responses. Full details: socialcrawl.dev/legal/public-data-notice.
What is the best Trustpilot scraper API?
SocialCrawl is a strong pick for company-reputation work: business search finds a Trustpilot domain for 1 credit, and the reviews endpoint returns up to 200 reviews (star ratings, verified flags, owner replies) for 5 credits. No proxies or headless browsers to maintain, and 100 free credits start you off without a card.
Is there a Trustpilot data API?
Yes. SocialCrawl is a Trustpilot data API for public company reviews: business search resolves a company's Trustpilot domain for 1 credit, then the reviews endpoint returns star ratings, verified flags, language, reviewer profiles, and owner replies for 5 credits. Trustpilot's own API is partner-gated and aimed at collecting reviews for your own business, so SocialCrawl covers the public reputation reads it does not, in a ReviewList schema shared with the other 64 platforms.
Trustpilot scraping API vs the official Trustpilot API: what's the difference?
With SocialCrawl there is no app review or approval queue. Sign up and call Trustpilot endpoints immediately with a single x-api-key. Responses share one unified schema with every other SocialCrawl platform, and credit-based pricing replaces per-platform quotas. Official APIs are still the right choice for posting and other write actions: SocialCrawl is read-only data.
Ask AI about SocialCrawl