POST /v1/places:searchText → endpoint removal
Google Places API (New)Deprecated, no date
Google Places API (New) deprecated the body parameter maxResultCount on POST /v1/places:searchText as of May 13, 2024, without announcing a shutdown date. The provider made this change to better meet developer needs. Calls that continue to rely on this parameter will eventually fail once it is fully removed.
Calls it hits
POST /v1/places:searchTextbody parameter maxResultCount
What to use instead of these calls
Use pageSize to set the number of results per page.
In Google Places API (New)'s words
To better meet developer needs, the Text Search (New) field maxResultCount in the Places API (New) is deprecated as of May 13, 2024.
Facts
- API
- Google Places API (New)
places.googleapis.com - Kind
- Endpoint removal
- Announced
- May 13, 2024
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Google Places API (New)'s own pages
Questions
When does this change take effect?
Google Places API (New) deprecated POST /v1/places:searchText, body parameter maxResultCount without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Google Places API (New) has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.