How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

TrustRadius Traffic Data API

Profile traffic reporting. GET /reports/traffic/products returns page views, visits and visitors per product per day alongside the matching category-level totals, so share-of-category is computable client-side. GET /reports/traffic/pages breaks the same window down by page type, page title and URL. Both accept ISO 8601 start-date/end-date filters, comma-separated product ids, skip/limit paging, and a format parameter for JSON or CSV.

TrustRadius Traffic Data API is one of 5 APIs that TrustRadius publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Analytics, Traffic, and Reporting. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, and authentication docs.

This API exposes 2 operations across 2 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.1.

Requests are made against a single base URL, https://api.trustradius.com/v1.

2 operations 2 paths 2 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.1
Base URL
https://api.trustradius.com/v1
Authentication
API Key
Resource Areas
1

Authentication & Security 1

TrustRadius Traffic Data API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-api-key (x-api-key).

  • x-api-key — All API calls must send an API key in the "x-api-key" HTTP header. TrustRadius clients can get their key from their Client Success Manager.

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.

Traffic Data 2
GET
/reports/traffic/pages
Gets page-level traffic data (page views and visits)
get_traffic_page_types 8 params → 200400404
GET
/reports/traffic/products
Gets aggregate traffic data (page views and visits)
get_traffic_products 8 params → 200400404

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are TrafficProduct (12 properties), TrafficPage (9 properties). Each schema is shown below with its type and property counts.

TrafficPage
object
9 properties
TrafficProduct
object
12 properties 8 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

trustradius-traffic-data-api-openapi.yml Raw ↑

Other APIs TrustRadius publishes across the network.

TrustRadius Product Data API
TrustRadius Downstream Intent Data API
TrustRadius TrustQuotes Content Syndication API
TrustRadius Legacy Visitor Insights API
Where this information came from

This is an independent, third-party profile of TrustRadius Traffic Data API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.