Assigned
Status Update
No update yet.
Comments
ca...@google.com
Thanks for your suggestion! We are currently evaluating this request, but do not have any plans to implement it at the moment. Please star to add your vote and receive further updates, and feel free to add any comments to discuss your use case.
ol...@gmail.com
I've transitioned from this team. Thanks!
av...@gmail.com
Hi, is there any movement on this request ?
Thanks,
Avinash
Thanks,
Avinash
th...@gmail.com
Would love to migrate from old API to new but this feature is critical and still missing. Can we have an update on this?
mb...@g.trelatech.com
Agreed. Would like to start using Place Details (New) but this critical feature is preventing us from migrating.
Description
#REMINDER: Please do not disclose any possible PII such as: email address, IP, contact number, any part of name, project numbers and billing accounts as these information may violate security and privacy. Comments or attachments that include PII will be removed and restricted from public viewing.
Furthermore, please refrain from replying to a comment as this will make your email address visible. Instead, you may use the Issue Tracker’s comment feature for your replies.
It is OK to share your API Project ID, but _not_ API keys or client ID credentials.
To learn more about personal data, visit
===========================================================================================
Feature Request
-----------------------
What would you like to see us add to this API?
About Place Details (New).
1 - We would like an option for the reviews to return the 'Latest' reviews, not the most relevant, just like it was in the previous Place Details API (what you call a legacy API).
The way the Place Details (New) is is not usable to us and we will have to stop using it.
2 - We would also like to have an option to return more than 5 latest reviews per request. It would be the best for us.
3 - If you stop the Legacy Place Details API, we will stop using it altogether because the new Place Details is not usable for us.
Thank you,
Oleg