Autocomplete API 更新
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
2015年7月27日星期一
原文：
Update on the Autocomplete API
作者：
Peter Chiu, Autocomplete team
Google 搜尋提供的自動完成服務會在使用者輸入搜尋字詞的當下，嘗試預測查詢字詞。多年來，許多開發人員使用非官方和未發佈的 API，將自動完成的結果與自己的服務進行整合，而且完全不加以限制。後來，發現自動完成 API 的開發人員整合了自動完成服務，而且讓這項服務獨立於 Google 搜尋之外。
開發人員社群會透過未發佈的 API，對特定 Google 服務進行反向工程，而且多次獲得驚人的成果。舉例來說，我們看到創意十足的工程師將地圖資料和其他資料來源加以結合，創造出絕佳的功用，因此我們在幾個月之後，決定將 Google Maps API 列為正式受支援的 API。我們目前支援
超過 80 個 API
，可供開發人員用來將 Google 服務整合至個人的應用程式。
不過，在某些情況下，使用不支援且未發佈的 API，也可能導致該 API 停止提供服務。這個情況就是其中一例。
我們建立自動完成功能是為了讓搜尋功能更加完善，從未想過這項功能會用於與預測使用者搜尋查詢完全無關的用途。長久下來我們瞭解到一件事，雖然我們想像得到將自動完成資料資訊提供運用在與搜尋結果無關的用途上，可能會帶來些許價值，但總體來說，我們自動完成功能的內容原本就是為了與網路搜尋結果配合使用，而且已針對這項用途進行最佳化，因此將這項功能應用在網路搜尋之外的情況並無法為使用者提供實質助益。
為了讓搜尋中的自動完成功能維持完整性，我們將於2015年8月10日起，限制未經授權的人士存取尚未發佈的自動完成 API。我們想確保使用者能受惠於自動完成功能的原始設計功用，也就是與搜尋緊密結合的服務。我們相信這樣才能使這兩項服務提供最佳使用體驗。
對於仍想在個人網站上使用自動完成服務的發佈者和開發人員，我們有個替代方案。Google 自訂搜尋引擎可讓網站繼續使用搜尋功能中的自動完成功能。這項異動不會影響到任何已使用 Google CSE 的合作夥伴。至於其他使用者，如果您想在2015年8月10日後繼續使用自動完成功能，請參閱我們 CSE 申請網頁中的說明。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2015-07-01 (世界標準時間)。
[null,null,["上次更新時間：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"]]
