# GET /customsearch/v1/siterestrict stops working

Calls to GET /customsearch/v1/siterestrict on Google APIs stopped working on January 8, 2025.

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.

## What to use instead

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.

- API: Google APIs (www.googleapis.com)
- Kind: Endpoint removal
- Takes effect: January 8, 2025
- Calls after that day: fail
- Calls it hits: `GET /customsearch/v1/siterestrict`
- Source: [Announcement](https://developers.google.com/custom-search/v1/site_restricted_api)
- Verified: October 26, 2026, against Google APIs's own pages
- Page: https://www.okapi.bot/providers/google-apis/breaking-changes/get-customsearch-v1-siterestrict-stops-working/

## 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.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent