Google Custom Search JSON API ends Jan 1, 2027: what to do
If your app calls https://www.googleapis.com/customsearch/v1 , it has a hard deadline. Google closed the Custom Search JSON API to new customers on January 20, 2026 , and the API shuts down on January 1, 2027 . After that, requests fail. This post covers the timeline, what your options are, and how to migrate with the smallest possible diff. Deadline: January 1, 2027. Plan to switch at least two…
Google Custom Search JSON API ends on January 1, 2027. The API was closed to new customers on January 20, 2026, and no official successor was announced. You must migrate your applications before the shutdown. The partner-only Web Search Service API exists but does not replace the JSON API. After the shutdown, requests to https://www.googleapis.com/customsearch/v1 will fail.
You can switch to SerpKite, which offers a similar endpoint with comparable parameters and response format. Swapping the hostname and API key is the only code change required. SerpKite provides 2,500 free credits and charges $1.00 per 1,000 calls afterward. Plan your migration over ten weeks, testing the switch with real queries and comparing results. After the switch, disable the Custom Search API in Google Cloud to avoid further costs.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
