@philos1964 Your Place ID is ChIJY-iGu7dv5kcRCpZDFDDZba8 – you can see the data when you search in Google for “Philippe LECOMTE Concepteur de sites Web”, right click on “Leave a Review” and look at the data-pid for the button. Also, this link works:
https://search.google.com/local/reviews?placeid=ChIJY-iGu7dv5kcRCpZDFDDZba8
However, the Google API is still returning “Not Found” whenever a request is made with this Place ID. It may be something relating to regions rather than a specific location. Whatever it is, Google is simply not sending any data and returning a “Not Found” error.
When searching for a fix to this returned data, I found this archived information from Google:
You may occasionally receive a NOT_FOUND status code when you use a saved place ID.
A place ID may become obsolete if a business closes or moves to a new location.
Place IDs may change due to large-scale updates on the Google Maps database. In such cases, a place may receive a new place ID, and the old ID returns a NOT_FOUND response.
Best practice is to refresh your stored place IDs periodically. You can refresh Place IDs free of charge, by making a Place Details request, specifying only the ID field in the fields parameter. This will trigger the Places Details – ID Refresh SKU.
However, this request might also return NOT_FOUND status code. One strategy is to store the original request that returned each place ID. If a place ID becomes invalid, you can re-issue that request to get fresh results. These results may or may not include the original place. The request is chargeable.
I will continue to investigate this issue, but without the source data in some form, I don’t see a viable way to update the reviews. In the meantime, I will see what I can do to present data already stored locally to avoid interruptions when Google stops sending new data.