有关自动填充 API 的一项重要更新
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
2015年7月27日星期一
原文：
Update on the Autocomplete API
作者：
Peter Chiu, Autocomplete team
Google 搜索提供了一项自动填充服务，该服务会在用户输入查询字词时尝试预测他们要查询的内容。多年来，很多开发者都通过一款未公开发布的非官方 API 在自己的服务中集成了自动填充结果。由于该 API 对此没有任何限制，因此，发现这款自动填充 API 的开发者能够集成自动填充服务，并使该服务独立于 Google 搜索。
开发者群体经常会通过未公开发布的 API 对 Google 服务进行逆向工程，并且有很多次都取得了不错的成果。Google Maps API 就是一个例子。我们看到，富有创新精神的工程师通过将地图数据与其他数据来源加以整合，取得了意想不到的效果，因此在数月之后，我们将该 API 变成了一款正式发布且受支持的 API。我们目前支持
80 多款 API
，开发者可以利用它们将 Google 服务和数据集成到自己的应用中。
不过，有时候使用不受支持且未公开发布的 API 也存在风险，比如使用的 API 不再可用。
我们开发自动填充功能的初衷是为了完善 Google 搜索服务，从未想过将其用于与预测用户的搜索查询无关的用途。随着时间的推移，我们认识到，虽然我们能够想象出自动填充数据 Feed 的一些其他可能有价值的用途，但总体来说，我们优化自动填充内容的目的是为了帮助用户更快速地获得搜索结果，而在网络搜索之外的环境中，这些内容并不能给用户带来实质性的好处。
为了使作为 Google 搜索一部分的自动填充功能保持完整性，自 2015年8月10日起，我们将限制用户在未经授权的情况下使用未公开发布的自动填充 API。我们希望确保用户按我们的设计初衷使用自动填充功能，也就是将它与 Google 搜索结合使用。我们相信这有助于使这两项服务都能实现最好的用户体验。
对于仍希望在自己的网站上使用自动填充服务的发布商和开发者，我们提供了一个替代方案。通过 Google 自定义搜索引擎 (CSE)，网站可以继续将自动填充功能与 Google 搜索功能结合使用。此项变更不会影响已经在使用 Google CSE 的合作伙伴。对于其他合作伙伴，如果希望在 2015年8月10日后继续使用自动填充功能，请参阅我们的 CSE 注册页面。
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2015-07-01。
[null,null,["最后更新时间 (UTC)：2015-07-01。"],[[["\u003cp\u003eGoogle will restrict unauthorized access to the unpublished autocomplete API starting August 10, 2015.\u003c/p\u003e\n"],["\u003cp\u003eGoogle's autocomplete service was designed as a complement to Search and not intended for use outside of this context.\u003c/p\u003e\n"],["\u003cp\u003eGoogle encourages the use of Google Custom Search Engine (CSE) as an alternative for sites needing autocomplete functionality.\u003c/p\u003e\n"],["\u003cp\u003eWhile reverse-engineering of Google services has sometimes led to valuable outcomes, the autocomplete API is being restricted to maintain its integrity and intended user experience.\u003c/p\u003e\n"]]],["Google will restrict unauthorized access to its unpublished autocomplete API on August 10th, 2015, due to its intended use being solely within Google Search. Previously, developers used this API independently, but Google believes the feature is optimized for use with search results. They are stopping support due to a lack of user benefit. An alternative is provided through Google Custom Search Engine (CSE), allowing sites to maintain autocomplete when linked to search functionality.\n"],null,["# Update on the Autocomplete API\n\nFriday, July 24, 2015\n\n\nGoogle Search provides an autocomplete service that attempts to predict a query before a user\nfinishes typing. For years, a number of developers have integrated the results of autocomplete\nwithin their own services using a non-official, non-published API that also had no restrictions on\nit. Developers who discovered the autocomplete API were then able to incorporate autocomplete\nservices, independent of Google Search.\n\n\nThere have been multiple times in which the developer community's reverse-engineering of a Google\nservice via an unpublished API has led to great things. The Google Maps API, for example, became a\nformal supported API months after seeing what creative engineers could do combining map data with\nother data sources. We currently support\n[more than 80 APIs](/apis-explorer) that\ndevelopers can use to integrate Google services and data into their applications.\n\n\nHowever, there are some times when using an unsupported, unpublished API also carries the risk\nthat the API will stop being be available. This is one of those situations.\n\n\nWe built autocomplete as a complement to Search, and never intended that it would exist\ndisconnected from the purpose of anticipating user search queries. Over time we've realized that\nwhile we can conceive of uses for an autocomplete data feed outside of search results that may be\nvaluable, overall the content of our automatic completions are optimized and intended to be used\nin conjunction with web search results, and outside of the context of a web search don't provide a\nmeaningful user benefit.\n\n\nIn the interest of maintaining the integrity of autocomplete as part of Search, we will be\nrestricting unauthorized access to the unpublished autocomplete API as of August 10th, 2015. We\nwant to ensure that users experience autocomplete as it was designed to be used---as a service\nclosely tied to Search. We believe this provides the best user experience for both services.\n\n\nFor publishers and developers who still want to use the autocomplete service for their site, we\nhave an alternative. Google Custom Search Engine allows sites to maintain autocomplete\nfunctionality in connection with Search functionality. Any partner already using Google CSE will\nbe unaffected by this change. For others, if you want autocomplete functionality after August\n10th, 2015, please see our CSE sign-up page.\n\nPosted by Peter Chiu on behalf of the Autocomplete team"]]
