Skip to content

Reviews Guide ​

Reviews can be retrieved for synchronization, analytics, dashboards, and external reporting.

Endpoints ​

MethodPathPurpose
GET/api/2026-04/reviewsList reviews for the API key context.
GET/api/2026-04/reviews/{id}Read one review by Revi review ID.
GET/api/2026-04/products/{id_product}/reviewsList reviews for one product.

List Reviews ​

bash
curl "https://api.revi.io/api/2026-04/reviews?from_date=2026-01-01&per_page=25&sort=date_desc" \
  -H "Accept: application/json" \
  -H "X-API-KEY: revi_test_xxxxxxxxx"

Supported filters:

FilterDescription
pagePage number, starting at 1.
per_pagePage size, from 1 to 100. Default is 25.
from_idReviews with an ID greater than or equal to the value.
to_idReviews with an ID less than or equal to the value.
from_dateReviews from this date onward.
to_dateReviews up to this date.
ratingExact rating.
min_ratingMinimum rating.
has_replytrue for reviews with a business reply, false for reviews without one.
typeshop or product.
id_productExternal product ID.
id_storeStore ID, or a comma-separated list of numeric store IDs.
langLanguage code.
sortdate_desc, date_asc, rating_desc, or rating_asc.

Review Shape ​

Review list and detail responses can include:

FieldDescription
idRevi review ID.
id_storeStore ID.
id_productExternal product ID for product reviews.
id_combinationExternal product combination ID when available.
typeshop or product.
customer_namePublic reviewer name; empty for anonymous reviews.
dateReview date.
commentReview text.
ratingRating value.
langReview language.
anonymousWhether the review is anonymous.
has_replyWhether the review has a business reply.

The product-specific endpoint GET /api/2026-04/products/{id_product}/reviews returns a smaller review row for catalog pages: id, customer_name, comment, rating, lang, anonymous, and date.

Pagination ​

List responses include pagination metadata:

json
{
  "meta": {
    "api_version": "2026-04",
    "pagination": {
      "page": 1,
      "per_page": 25,
      "total": 100,
      "total_pages": 4
    }
  }
}

Privacy Notes ​

The 2026-04 review endpoints return display data only: they omit email, surname, IP and order identifiers. This is a privacy restriction of the existing response contract. Integrations that used those fields must stop relying on them here.

Server-side integrations that need personal data use 2026-10 with a Bearer API client, an authorized store and reviews:read. The additional personal_data:read scope permits available email, surname and order fields on review list/detail; product review rows remain smaller and do not include email. Without that scope, reviewer identity and order fields are omitted. Anonymous reviews never include reviewer identity or order identifiers, even with that scope.

Keep credentials on your server. A display response is not permission to publish a private credential in browser code. Only request and retain fields necessary for your integration.

Public API documentation for Revi.