Trustpilot Search API — Search Businesses by Keyword
Send a keyword and this source returns matching Trustpilot businesses as data: name, domain, rating and review count.
{
"session_id": "11111111-1111-1111-1111-111111111111",
"kind": "trustpilot_business_search",
"query": "hubspot",
"max_items": 2,
"partial": false,
"human": "# Trustpilot business search\n\n- **Search term:** hubspot\n- **Max items:** 2\n- **Records returned:** 2\n- **Proxy traffic:** 566.3 KB",
"machine": {
"total_items": 2,
"items": [
{
"id": "551230910000ff00057e45c3",
"name": "HubSpot",
"url": "https://www.trustpilot.com/review/hubspot.com",
"website": "https://www.hubspot.com/",
"image": "https://s3-eu-west-1.amazonaws.com/tpd/logos/551230910000ff00057e45c3/0x0.png",
"rating": 1.5,
"review_count": 1169,
"location": "United States"
},
{
"id": "650f475ce38c175d3a5d874d",
"name": "Hubspot",
"url": "https://www.trustpilot.com/review/academy.hubspot.com",
"website": "https://academy.hubspot.com",
"image": null,
"rating": 0,
"review_count": 0,
"location": "United States"
}
],
"proxy_traffic_bytes": 579882
},
"total_points": 2
}- You send
- A search keyword
- You get back
- Matching businesses with name, domain, rating and review count
- Coverage
- Businesses with a public Trustpilot profile.
- Price
- 1 point per returned result, up to 300 per request — $1 per 1,000
- Billed per record actually returned, capped by max_items. A search that matches nothing costs nothing.
Ways to get this data
Three approaches teams use today, and where each one runs into trouble.
| Approach | What it takes | Cost | Trade-off |
|---|---|---|---|
| Searching Trustpilot by hand | Type a term, scroll, note down what shows up | Free, and slow | Fine for a one-off check, not for tracking many companies |
| Building a scraper | Write it, host it, repair it when the layout moves | Engineering time | A maintenance commitment for something that isn't your product |
| NeuralVerge | One request per keyword | $1 per 1,000, misses not billed | Returns what Trustpilot's search returns — its own ranking, not a market truth |
What you get back
Every field in the response shown above.
| Field | Type | Description |
|---|---|---|
partial | boolean | True if the search hit its time budget and stopped early — re-run with a smaller max_items for a complete result. |
total_items | number | How many businesses came back. |
items | array | Matching businesses, in Trustpilot's search order. |
items[].id | string | Trustpilot's internal business ID. |
items[].name | string | Business name. |
items[].url | string | Trustpilot profile URL. |
items[].website | string | null | The business's own website, when Trustpilot has one. |
items[].image | string | null | Business logo image URL, when Trustpilot has one. |
items[].rating | number | Overall rating, or 0 for a profile with no reviews yet. |
items[].review_count | number | Total number of reviews. |
items[].location | string | null | Business location, when Trustpilot publishes one. |
proxy_traffic_bytes | number | Size of the raw page data collected to build this result. |
How to run it
The same lookup works from the app, the API, or as a tool an agent can call mid-task.
This endpoint is synchronous: the call blocks until the search completes and returns the matching businesses directly. query is required; max_items is optional (1-300, default 25). If a search hits its time budget before finishing, the response comes back with partial: true and whatever it found so far — re-run with a smaller max_items for a complete result.
curl -X POST https://api.neuralverge.ai/functions/v1/run-trustpilot-search \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "query": "hubspot", "max_items": 25 }'What teams use it for
Where this field shows up in an actual workflow.
Find the Trustpilot profile for a business name before you know its exact domain.
Search a list of company names to see which have a Trustpilot presence worth tracking.
See who else shows up on Trustpilot for a category or brand term.
Collect domains here, then pull full profiles or reviews for the ones that matter.
Coverage, freshness and limits
What this source covers, how fresh it is, and where it stops.
Businesses with a public Trustpilot profile.
Searched at request time.
This source returns publicly visible business information, stamped with the query it was read from and a session id you can trace.
- —Ranking reflects Trustpilot's own search algorithm, which factors in more than rating.
- —A keyword with no exact match can still return loosely related businesses.
- —Very small or new businesses may not have a Trustpilot profile at all.
Questions, answered
Yes — every Data Source endpoint, including this one, is synchronous: the scrape runs inside the request and the result comes back in the same response, no polling. If a scrape hits its time budget before finishing, the response comes back with partial: true and whatever records it collected so far — re-run with a smaller max_items to get a complete result instead of a partial one.
Related sources
Try trustpilot search on your own data
One request format across every source in the catalog.