Google Custom Search JSON API
GET /customsearch/v1/siterestrict endpoint removal
Stopped workingSubscribe to Google Custom Search JSON APIShare
On January 8, 2025, the GET /customsearch/v1/siterestrict endpoint stopped serving traffic. Requests made to this endpoint fail after that date. The change permanently disables this site-restricted search route.
Calls it hits
GET /customsearch/v1/siterestrict
What to use instead of these calls
Move the site-restricted search to Vertex AI Search on Google Cloud. 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
The Custom Search Site Restricted JSON API will cease to serve traffic on January 8, 2025, requiring customers to transition to Google Cloud's Vertex AI Search.
Facts
- API
- Google Custom Search JSON API
customsearch.googleapis.com - Kind
- Endpoint removal
- Takes effect
- January 8, 2025
- 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/siterestrict on Google Custom Search JSON API stopped working on January 8, 2025.
What happens to calls after January 8, 2025?
They have failed since January 8, 2025.
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*Endpoint removal Stops workingin 56 days
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.