Google APIs
GET /customsearch/v1* endpoint removal
Stops workingSubscribe to Google APIsShare
On January 1, 2027, the GET /customsearch/v1* endpoint will stop working. Existing customers have until that date to transition to an alternative solution. Any calls made to GET /customsearch/v1* after this date will fail.
Calls it hits
GET /customsearch/v1*
What to use instead of these calls
Move to Vertex AI Search for searches covering up to 50 domains, or contact Google about its full web search solution. Note that Vertex AI Search is a separate Google Cloud product requiring its own setup and pricing.
Vertex AI Search is another Google Cloud product, with its own setup and pricing.
In Google APIs's words
Existing Custom Search JSON API customers have until January 1, 2027 to transition to an alternative solution.
Facts
- API
- Google APIs
www.googleapis.com - Kind
- Endpoint removal
- Takes effect
- January 1, 2027
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Google APIs's own pages
Questions
When does this change take effect?
Calls to GET /customsearch/v1* on Google APIs stop working on January 1, 2027.
What happens to calls after January 1, 2027?
They fail from that day.
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.
More from Google APIs 8
-
GET /youtube/v3/searchParameter removal Stopped working -
POST /youtube/v3/comments/markAsSpamEndpoint removal Stopped working -
/youtube/v3/captionsParameter removal Stopped working -
GET /youtube/v3/commentThreadsParameter removal Stopped working -
GET /analytics/v3/data/*Version retirement Stopped working -
/androidcheck/v1/*Removal Stopped working -
GET /customsearch/v1/siterestrictEndpoint removal Stopped working -
No date
/drive/v3/files/{id}/permissions*Parameter removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix before January 1, 2027.