Google Custom Search JSON API
GET /customsearch/v1* endpoint removal
Stops workingSubscribe to Google Custom Search JSON APIShare
On January 1, 2027, the Google Custom Search JSON API will shut down GET /customsearch/v1* calls. Requests sent to customsearch.googleapis.com using these endpoints will fail after that day. Existing customers have until this date to transition to an alternative solution.
Calls it hits
GET /customsearch/v1*
What to use instead of these calls
Move to Vertex AI Search for up to 50 domains, or contact Google about its full web search solution. Transitioning requires more than updating an identifier, as Vertex AI Search is a separate Google Cloud product with its own setup and pricing.
Vertex AI Search is another Google Cloud product, with its own setup and pricing.
In Google Custom Search JSON API's words
Existing Custom Search JSON API customers have until January 1, 2027 to transition to an alternative solution.
Facts
- API
- Google Custom Search JSON API
customsearch.googleapis.com - Kind
- Endpoint removal
- Takes effect
- January 1, 2027
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Google Custom Search JSON API's own pages
Questions
When does this change take effect?
Calls to GET /customsearch/v1* on Google Custom Search JSON API 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 Custom Search JSON API 1
-
GET /customsearch/v1/siterestrictEndpoint removal Stopped working
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.