IssueTracker

#IMPORTANT: This template is intended to be used for Feature Requests concerning the Text Search (New) method for the service “Places API (New)” (“places.googleapis.com”), documented at https://developers.google.com/maps/documentation/places/web-service/search-textual.

This service is currently in the Preview launch stage. Google provides no SLAs or technical support commitments for Preview products. Unless stated otherwise by Google, Preview offerings are intended for use in test environments only.

To learn more about the Preview launch stage, see https://developers.google.com/maps/launch-stages#preview.

This template is not intended to be used for reports concerning the Text Search method for the service “Places API” (“places-backend.googleapis.com”), documented at https://developers.google.com/maps/documentation/places/web-service/search-text.

===========================================================================================

#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 https://en.wikipedia.org/wiki/Personal_data

===========================================================================================

Feature Request

What would you like to see us add to this API?

I would like to see a pagenation token similar to the old Places API for nearby search. The New places API has no such token, limiting requests to 20 per API call. This limit is tiny and makes it difficult to really browse options. I'm building a personal project where people can browse local restaurants, without knowing exactly what they want, but I cannot let them browse as it only returns 20 results and is extremely limited. Again, this existed on the old places api nearby search with the key next_page_token. I believe it should be implemented similarly.

(This Feature Request is about the Text Search endpoint for the service “Places API (New)” (“places.googleapis.com”), documented at https://developers.google.com/maps/documentation/places/web-service/search-textual)