Improved
October 26, 2026: updated_at now changes when a review's reply or removal request changes
11 days ago by Gopal Jha
Type: improvement (not a breaking change)
A review's updated_at now moves whenever anything you see on the review changes, including its reply and its removal request (flag). Before this release, it only moved when the review itself changed. So the updated_since filter alone now keeps your copy of reviews, replies and flags current.
What counts as a change
Already counted:
- A new review
- An edit to the review's rating, text, reviewer name or date
- A moderation change, such as hidden or suppressed
- A removal or restore
Now also counted:
- A reply written, edited or deleted, in Shout About Us or directly on the review site
- A change to a reply's posting status (pending, posted or failed)
- A removal request (flag) created, updated or withdrawn
Affected endpoints
POST /api/v1/partner/report/review-response/feed(Get reviews, partner)POST /api/v1/reports/response/feed(Review feed, account)
On both endpoints, the change applies to the updated_at field, the updated_since filter and sort_field: updated_at.
Every other endpoint that returns a review's updated_at follows the same rule. That includes the partner moderation feed, GET /api/v1/partner/admin/reviews/feed.
What hasn't changed
- No fields, parameters or response shapes changed.
- Webhooks are unchanged. Reply and flag changes still arrive as
response_*andflag_*events.cache_invalidationis still sent only for review changes, not when only a reply or flag changed. response_dateis still the time the reply was posted on the review site.
What you should do
- Run one full resync once this release is live. Reply and flag changes made before it didn't move
updated_at, so earlier incremental syncs may have missed some. Page through each location withlimit: 100and no date filter, then go back to your normal schedule. - Expect more reviews per sync. A review now comes back when only its reply or flag changed, for example when a reply goes from pending to posted. Keep updating each review by its
id. - Use polling as your safety net. Calling the feed with
updated_sinceandinclude_removed: truereturns every change. Webhooks only tell you sooner.
No code changes are needed.
