GET /customsearch/v1/siterestrict → endpoint removal
Google APIsStopped working
On January 8, 2025, the endpoint GET /customsearch/v1/siterestrict stopped working. Calls to this endpoint now fail. The API ceased to serve traffic on that date.
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 product with its own setup and pricing.
Vertex AI Search is another Google Cloud product, with its own setup and pricing.
In Google APIs'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 APIs
www.googleapis.com - Kind
- Endpoint removal
- Takes effect
- January 8, 2025
- 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/siterestrict on Google APIs 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 APIs 6
-
GET /youtube/v3/searchEndpoint removal Stopped working -
POST /youtube/v3/comments/markAsSpamEndpoint removal Stopped working -
/youtube/v3/captionsEndpoint removal Stopped working -
GET /youtube/v3/commentThreadsEndpoint removal Stopped working -
GET /analytics/v3/data/*Version retirement Stopped working -
/androidcheck/v1/*Endpoint removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.