People API has a method (searchContacts) which caters to searching contacts. However, it's only capped at 10 results/contacts returned. I would like to know if there is another alternative method or functionality that would search and return more or less 100 results.
Unfortunately, what you want cannot be achieved.
However, what you can do in this situation is to file a feature request on Google's Issue Tracker here and provide all the needed details.
Related
Just noticed today the following announcement:
Google Contacts API is now deprecated and is scheduled for sunset on June 15, 2021. Apps should instead use the People API.
Which is fine except the fact that People API does not provide any way to search contacts like the old Contacts API provided with ?q=.
Fulltext query on contacts data fields. The API currently supports simple search queries such as q=term1 term2 term3 and exact search queries such as q="term1 term2 term3"
Is there any way to do this simple text searching using People API?
So far it is not possible, but there is a feature request for it open on Google's Public Issue Tracker.
Give it a "star" to indicate that you are also interested in the feature - this will help to increase visibility.
I'm reading the documentation of GM-APIs, I found the section relative to "Places", but I can't find anything to get the information about the per-hour number of customers for a certain place.
Do you know whenever you search a place on GMaps, there is an indication of the frequency of customers, in that way you can know if the place will be busy or empty.
Is there any way to retrieve that information through Google Maps API?
Currently, there is no available feature in Google Maps API that could get the exact number or the of people in an establishment to determine its busiest time of the day.
However, there is an existing Feature Request in Google Map Platform's Public issue tracker to expose the place's popular times which seems to be related to the feature you are looking for.
Here's the link to that feature request: https://issuetracker.google.com/35827350. You can star/favorite this feature request and feel free to leave a comment there regarding your use case for additional information as well.
I'm using the google maps distance matrix javascript API to query the travel time from one point to about 50 destinations.
in order to do this, I need to break my query up into multiple chunks, since the google maps API allows only a maximum of 25 destinations per request.
the problem that I'm having is the synchronization of the request and the result.
other APIs offer the option to include a key that lets the developer match a request and an asynchronous result.
however, since such a parameter is missing from the request specification, I have no idea how to make sure that I'm matching the right data to my incoming results.
I would be glad for a "clean" workaround - currently the only idea that I'm having is to have a unique number of destinations for each request, for instance the first with 25, the next with 24 destinations and so on. but I would not consider this a satisfactory approach.
thank you
What is an efficient way to find recently updated Google contacts?
The obvious solution to retrieve all contacts with ContactsApp.getContacts() and iterate through all of them with getLastUpdated() doesn't seem particularly efficient and I am worried that such a code will exceed the time allowed if there are several thousand contacts.
Thanks.
You cant with ContactsApp. You can use urlFetch and use the raw contacts v3 api. Use a query using updated-min, remember what your last updated-min was so you only get ghe ones updated since your last call. See the api and this: https://developers.google.com/google-apps/contacts/v3/reference#Parameters
I want to use Google Places Autocomplete API to provide search-while-typing for an Android app.
the Autocomplete API returns IDs and References, requiring an iteration through the results to get the details (such as name and geometry) for each place, this is slow and results in a bad user experience. also, many API calls are done for each key press.
is there a better way to provide such searching capability with Google Places ?
Is there a reason you need to have the geometry for each possible autocomplete place after each keypress of the API? Showing this seems like generally it would not be a great user experience, and is not what the Autocomplete API was designed for.
In theory the name (description) should be enough for the user to decide which item they're interested in, and then after a user has actually selected something you can request additional details as needed.
On the other hand if you already have some information about the name of the place, you could use the Places API (not Autocomplete) to get additional details of matching nearby places:
https://developers.google.com/maps/documentation/places/#PlaceSearchResponses