# TrustRadius

> TrustRadius is a B2B buyer-intelligence and software-review platform. Buyers read in-depth verified
> reviews; software vendors buy packages that turn those reviews into demand — licensed review quotes,
> downstream intent data showing which accounts are researching them and their competitors, and
> traffic/visitor-insights reporting on their TrustRadius product profiles. TrustRadius is part of
> HG Insights. The TrustRadius Public API is the machine surface for the vendor side of that product.

Generated by API Evangelist on 2026-08-14 from the provider-published OpenAPI and developer portal.
TrustRadius does not publish an llms.txt of its own — every /llms.txt probe returned 404 (or 403 at
the Cloudflare edge). Source of truth is https://apidocs.trustradius.com/.

## The API in one paragraph

One REST API, base `https://api.trustradius.com/v1`, eleven operations, all GET. Authentication is a
single opaque API key in the lowercase `x-api-key` HTTP header, issued per vendor account from the
Vendor Portal (Integrations > "Get API key") or by a TrustRadius Client Success Manager. Access is
tied to a paid vendor package — there is no free or self-serve developer tier. Every response is JSON
by default; add `?format=csv` for CSV. Documented budget: 10 requests per second (600 per minute).

## Start here

Nothing else is callable until you resolve identifiers:

    curl -H 'x-api-key: YOUR_KEY' \
      'https://api.trustradius.com/v1/product-ids?products=<product-slug>'

The slug is the string in a www.trustradius.com product URL. The response carries the product `_id`
and the owning `vendor._id`. Called with no parameters as a vendor, it returns every published
product on your own profile. Multiple ids are always passed as a comma-separated list.

## Operations

Product Data
- GET /product-ids — resolve product and vendor ids from slugs (`product_ids_get`)
- GET /product-scores — TrustRadius (TR) Score, star score, review counts (`product_scores`)

Intent Data
- GET /intent — downstream intent activity by account and activity type (`intent_data`)

Traffic Data
- GET /reports/traffic/products — page views, visits, visitors per product per day (`get_traffic_products`)
- GET /reports/traffic/pages — page-level page views and visitors by page type/URL (`get_traffic_page_types`)

TrustQuotes
- GET /trustquotes — licensed review excerpts for syndication (`trustquotes_get`)
- GET /tags — the tag vocabulary used to filter TrustQuotes (`tags_get`)
- GET /reports/syndication/tqw/pages — TrustQuotes for Web widget performance (`tqw_pages_get`)

Legacy (provider-tagged "Legacy"; no replacement is documented)
- GET /reports/visitor-insights/companies — identified-company firmographics and visits (`visitor_insights_report`)
- GET /reports/visitor-insights/pages — identified-company visits with page detail (`visitor_insights_report_pages_get`)
- GET /accounts/{account_id} — one identified company with visit activity (`account_details`)

## Conventions an agent must know

- Auth: `x-api-key: <key>` header. Lowercase. No OAuth, no scopes, no token exchange.
- Format: `?format=json` (default) or `?format=csv`. The Accept header is ignored — this API does
  not do HTTP content negotiation.
- Paging: `skip` (>=0) and `limit` (>=1). No cursor, no total count, no Link header. Page until a
  short page comes back; that is the only end-of-data signal.
- Sorting: `sort=field1,-field2`. A leading hyphen means descending.
- Sparse fields: `fields=a,b,c`.
- Date filters: report endpoints use `start-date`/`end-date` (ISO 8601 dates); `/intent` uses
  `start_time`/`stop_time` (ISO 8601 date-times). The two families are named differently — do not
  generalize one to the other.
- Errors: 400 and 404 are declared on most operations but with no body schema; the observed edge
  deny is `{"message":"Forbidden"}` with HTTP 403. There is no RFC 9457 problem+json, no error code
  registry, no request-id header, and no documented 429.
- Rate limits: 10 req/s (600/min), published in the FAQ. No RateLimit-* response headers exist, so
  budget client-side.
- Idempotency: not applicable — every operation is a GET.

## What TrustRadius does not publish

No SDK in any package registry. No CLI. No MCP server. No A2A agent card. No webhooks or events
(the OpenAPI declares a `Webhooks` tag with zero operations attached to it). No /.well-known/
documents on any host. No changelog, no status page, no deprecation policy, no published SLA.

## Testing without a key

The developer portal auto-provisions a Stoplight Prism mock from the published spec at
`https://stoplight.io/mocks/trustradius/public-api/5138360`. It covers all eleven operations and
requires any non-empty `x-api-key` header value (it does not validate the key). It returns
schema-shaped placeholders, never real data, and it is hosted by Stoplight rather than TrustRadius.

## Links

- API documentation: https://apidocs.trustradius.com/
- API overview and auth: https://apidocs.trustradius.com/docs/public-api/ZG9jOjQ1Mg-trust-radius-api
- FAQ (ids, rate limit, multi-id syntax): https://apidocs.trustradius.com/docs/public-api/ZG9jOjMzODE1NA-faq
- Getting your API key: https://trustradius.freshdesk.com/support/solutions/articles/43000639047
- Help center: https://trustradius.freshdesk.com/support/solutions
- Vendor site: https://solutions.trustradius.com/
- Pricing and packaging: https://solutions.trustradius.com/pricing/
- Integrations: https://solutions.trustradius.com/integrations/
- Terms of use: https://www.trustradius.com/legal/terms-of-use
- Privacy policy: https://www.trustradius.com/legal/privacy-policy
- API questions: product@trustradius.com

## Integrations

TrustRadius intent data is designed to be activated in Salesforce, HubSpot, 6sense, Demandbase,
Marketo, LinkedIn Matched Audiences and Snowflake. See https://solutions.trustradius.com/integrations/.