The JSON All Reviews API gives you a combined, client-wide view of your reviews: a summary and paginated lists covering both product (customer) reviews and seller reviews, without needing a specific product ID.
It is a simpler alternative to the JSON Display API for building things like an “all reviews”
page or a client-wide trust badge, and works the same way as the Seller Reviews API and
AI Review Summaries API: call cr.testfreaks.com directly with your client ID.
Note: The All Reviews API must be enabled by TestFreaks for your client ID.
The API takes your client ID and returns a JSON response summarizing your product reviews and seller reviews, along with the location of the first page of each.
https://cr.testfreaks.com/all-reviews.json?client_id=your.client.id
The your.client.id part should be replaced with one of your assigned client IDs.
If you have multiple client IDs, for example one per market or brand, that should be combined into a single
“all reviews” summary, add each additional one as a linked_client_ids parameter:
https://cr.testfreaks.com/all-reviews.json?client_id=your.client.id&linked_client_ids[]=your.other.client.id
Note: The All Reviews API must be enabled by TestFreaks for every client ID involved — both
client_idand anylinked_client_ids. Talk to your TestFreaks contact if you’re not sure which of your client IDs should be linked together.
Example response:
{
"product_avg_score": 4.4,
"product_score_dist": [2, 3, 10, 35, 70],
"product_review_count": 120,
"seller_avg_score": 4.0,
"seller_score_dist": [1, 2, 7, 20, 50],
"seller_review_count": 80,
"product_review_url": "https://cr.testfreaks.com/all-reviews/product-reviews.json?client_id=your.client.id&limit=10",
"seller_review_url": "https://cr.testfreaks.com/all-reviews/seller-reviews.json?client_id=your.client.id&limit=10"
}
| Attribute | Description |
|---|---|
| product_avg_score | Combined average product review score (a decimal number between 1.0–5.0) |
| product_score_dist | Number of product reviews with score 1, 2, 3, 4, and 5 |
| product_review_count | Total number of product reviews |
| seller_avg_score | Combined average seller review score (a decimal number between 1.0–5.0) |
| seller_score_dist | Number of seller reviews with score 1, 2, 3, 4, and 5 |
| seller_review_count | Total number of seller reviews |
| product_review_url | API location of the first page of product reviews (only present if product_review_count is greater than 0) |
| seller_review_url | API location of the first page of seller reviews (only present if seller_review_count is greater than 0) |
Any linked_client_ids included in the request are automatically carried over into product_review_url and
seller_review_url, so you don’t need to repeat them yourself.
The product review URL (product_review_url) is the API location for the first page of product reviews, in JSON.
It can also be built directly:
https://cr.testfreaks.com/all-reviews/product-reviews.json?client_id=your.client.id
Example response:
{
"reviews": [
{
"type": "customer",
"source": "Your Site Name",
"domain": "yoursite.example",
"client_id": "your.client.id",
"author": "John D",
"date": "2023-09-19",
"score": 4,
"score_max": 5,
"title": "Great product",
"extract": "I really like the ACME ABC123.",
"pros": "Very durable, Long battery life",
"cons": "A bit expensive",
"lang": "en",
"verified_buyer": true,
"votes_up": 9,
"votes_down": 0,
"product": "ACME Product ABC123",
"product_id": "P001-02-BLK",
"product_url": "<url>",
"product_image_url": "<url>",
"brand": "ACME",
"recommended": true,
"feedback_url": "<url>",
"images": [],
"responses": [],
"question_answers": []
}
],
"next_page_url": "https://cr.testfreaks.com/all-reviews/product-reviews.json?client_id=your.client.id&offset=10"
}
Most fields have the same meaning as the customer review fields in the JSON Display
API: type, source, domain, author, date, lang, score, score_max, extract, pros, cons,
verified_buyer, votes_up, votes_down, feedback_url, images, responses, question_answers, and
original (for translated reviews).
A few fields are specific to this endpoint:
| Attribute | Description |
|---|---|
| client_id | The client ID the review belongs to (your client_id, or one of the linked_client_ids) |
| product | Product name, from your product feed |
| product_id | Your product ID |
| product_url | Product page URL, from your product feed (if available) |
| product_image_url | Product image URL, from your product feed (if available) |
| brand | Product manufacturer/brand, from your product feed (if available) |
| recommended | true/false if the reviewer indicated whether they recommend the product, otherwise omitted |
| properties | Answers to custom product properties, if any are configured |
The next_page_url field contains the URL for the next page of reviews, if available.
Note: Treat this URL as an opaque string. Do not modify or parse it. The format may change without notice.
The seller review URL (seller_review_url) is the API location for the first page of seller reviews, in the same
format as the Seller Reviews API. It can also be built directly:
https://cr.testfreaks.com/all-reviews/seller-reviews.json?client_id=your.client.id
Example response:
{
"seller_reviews": [
{
"author": "Sven Svensson",
"score": 5,
"score_max": 5,
"date": "2026-05-01",
"title": "Great service",
"extract": "Fast delivery and helpful support.",
"lang": "en",
"verified_buyer": true,
"votes_up": 3,
"votes_down": 0,
"feedback_url": "<url>",
"responses": [],
"question_answers": []
}
],
"next_page_url": "https://cr.testfreaks.com/all-reviews/seller-reviews.json?client_id=your.client.id&offset=10"
}
These fields have the same meaning as the customer review fields described above.
The next_page_url field contains the URL for the next page of seller reviews, if available.
By default the product and seller review URLs return the first 10 reviews, and return the location of the next 10
after that. The page size can be customized with the limit parameter (1–100), and offset can be used to access
following pages. For example:
&limit=10&offset=0
&limit=10&offset=10
&limit=10&offset=20
By default reviews are sorted by date, most recent first. The sort parameter can be used to change this:
sort=date:asc
sort=score
sort=score:asc
| Value | Description |
|---|---|
| (default) | Most recent first |
| date:asc | Oldest first |
| score | Highest score first |
| score:asc | Lowest score first |
When linked_client_ids are included, reviews for your primary client_id are returned first. Once those are
exhausted, reviews from the linked clients follow as a continuation of the same paginated list.
Add sections=0 to instead merge reviews from all client IDs into a single list, sorted together according to the
sort order above, regardless of which client ID they belong to:
§ions=0