more than 80 APIs<\/a> that
\n developers can use to integrate Google services and data into their applications.\n<\/p>\n\n However, there are some times when using an unsupported, unpublished API also carries the risk
\n that the API will stop being be available. This is one of those situations.\n<\/p>\n
\n We built autocomplete as a complement to Search, and never intended that it would exist
\n disconnected from the purpose of anticipating user search queries. Over time we’ve realized that
\n while we can conceive of uses for an autocomplete data feed outside of search results that may be
\n valuable, overall the content of our automatic completions are optimized and intended to be used
\n in conjunction with web search results, and outside of the context of a web search don’t provide a
\n meaningful user benefit.\n<\/p>\n
\n In the interest of maintaining the integrity of autocomplete as part of Search, we will be
\n restricting unauthorized access to the unpublished autocomplete API as of August 10th, 2015. We
\n want to ensure that users experience autocomplete as it was designed to be used—as a service
\n closely tied to Search. We believe this provides the best user experience for both services.\n<\/p>\n
\n For publishers and developers who still want to use the autocomplete service for their site, we
\n have an alternative. Google Custom Search Engine allows sites to maintain autocomplete
\n functionality in connection with Search functionality. Any partner already using Google CSE will
\n be unaffected by this change. For others, if you want autocomplete functionality after August
\n 10th, 2015, please see our CSE sign-up page.\n<\/p>\n
Posted by Peter Chiu on behalf of the Autocomplete team<\/p>\n","protected":false},"excerpt":{"rendered":"
Friday, July 24, 2015 Google Search provides an autocomplete service that attempts to predict a query before a user finishes typing. For years, a number of developers have integrated the results of autocomplete within their own services using a non-official, non-published API that also had no restrictions on it. Developers who discovered the autocomplete API […]<\/p>\n","protected":false},"menu_order":83360,"template":"","meta":{"footnotes":""},"ar_kb_kategori":[665],"ar_kb_etiket":[],"class_list":["post-24893","ar_kb","type-ar_kb","status-publish","has-post-thumbnail","hentry","ar_kb_kategori-blog"],"_links":{"self":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/24893","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb"}],"about":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/types\/ar_kb"}],"version-history":[{"count":0,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/24893\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media\/27075"}],"wp:attachment":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media?parent=24893"}],"wp:term":[{"taxonomy":"ar_kb_kategori","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_kategori?post=24893"},{"taxonomy":"ar_kb_etiket","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_etiket?post=24893"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}