Updated reviews & responses (Review Scraper API)

The way we handle updated reviews and responses works differently depending on which API you use, and how you use it.

Review Scraper API

With diff

As a reminder, the diff parameter makes it seamless to receive only the latest reviews from a given review profile each time you check.

In other words, we do the heavy computational lifting so you can rest assured to only ever receive fresh reviews. This has several implications which you may want to be aware of:

1. This does not handle the case where a user updates their review, for example:
   • User leaves a review on 1st June
   • We fetch it on 3rd June
   • User updates it on the 4th June

   In this case, we will not fetch that update.

2. This does not fetch responses for old reviews, for example:
   • If the user leaves a review on 1st June
   • We fetch it on 3rd June
   • Owner responds to the review on the 4th June

   In this case, we will not fetch that response.

If having these two cases covered is important to your use case, please see the next section below on not using the diff parameter.

Without diff

If you are not using the diff parameter, you have more flexibility in being able to fetch updates and review responses in a manner that you wish.

1. You could handle the case where a user updates their review
2. You could handle the case for syncing responses to old reviews

However, this will require some work on your end to avoid ingesting duplicate reviews, which is what the diff parameter provides out of the box.