Google Discontinues Custom Search API
Thousands of applications and services rely on this API for embedded search functionality.
Nine-month sunset window
Google announced it will retire the Custom Search API on January 1, 2027, giving developers and organizations nine months to migrate. The service has allowed third-party sites and applications to embed Google search capabilities for over a decade.
No replacement product has been announced. Organizations using the API will need to either build their own search infrastructure or turn to alternative providers.
Impact on existing integrations
The API powers search boxes on corporate sites, documentation portals, and specialized research tools. Many were built years ago with the expectation of long-term API stability.
Migration will require technical resources during an already constrained hiring environment. Smaller organizations may struggle to allocate engineering time before the deadline.
Pattern of API retirements
This follows a series of Google API sunsets in recent years, including parts of Google+ and several data APIs. Each retirement has prompted discussion about the risks of building on third-party platform dependencies.
The company has not stated a reason for the decision. Developer communities are now evaluating self-hosted search engines and services from vendors like Algolia and Elastic.