API
GET /v1/data/ratingsUse a signed-in session or a key with permission to read data. Keep keys on your server.
Read the API documentationREWALTO / BRAND SIGNALS
Every change in a product’s rating, rating count and review count, per retailer and pin code, by IST day.
Ratings over time tracks a product's star rating and its rating and review counts on each retailer, day by day. As of 17 Oct 2026: 10 retailers, updated daily at 13:30 IST. Reads cost 1 credit per 10 rating changes. Source: Rewalto's readings of public app pages.
Review the published rate before requesting records. A page is read only when you choose to run it.
Plan your filters
Choose a retailer, then narrow by its product ID, pin code and date range. Compare rating values and rating and review counts.
| Measure | Coverage | Context |
|---|---|---|
| Retailers | 10 marketplaces and quick-commerce appsMeasured 17 Oct 2026, 5:30 am IST | From the product pages and search results Rewalto already reads: no extra request. |
| What is kept | Changes onlyMeasured 17 Oct 2026, 5:30 am IST | A row is written on a day the rating, rating count or review count changed, so the history is a change log. |
| Rating changes kept | Not measured yetNot measured yet | Counted after the first daily run (23 Oct 2026). |
A live sample is not available yet. No example records are substituted. The catalogue entry describes the available fields.
Use the same dataset through the dashboard, API, CLI or an agent.
GET /v1/data/ratingsUse a signed-in session or a key with permission to read data. Keep keys on your server.
Read the API documentationrewalto data ratingsApply the same filters and page size as the API. Review the published rate first.
Set up the CLIlist_rating_changesConnect your agent at mcp.rewalto.com/mcp. Data access uses the same account permissions and rates.
Coverage, status, examples and published rates come from the catalogue entry. Measurement dates appear with each figure.