Google CSE REST API:不推荐使用 v1，是否有 v2? [英] Google CSE REST API : is v1 deprecated, is there a v2?

问题描述

作为 google CSE API 的许多用户，我最近收到一封来自Google 自定义搜索"的电子邮件，询问我请迁移到自定义搜索元素 API 2.0".我检查了文档，但他们只描述了如何集成谷歌搜索输入在一个网站中.我目前正在使用 Node.js 程序中 google cse 的 REST 端点，因此我无法使用它.有关 REST 端点的文档 仍然引用 V1，因此我有点失落.我想知道这个端点是否也已弃用并且很快就会停止工作，以及 API 的 v2 是否(或将要)通过 REST 端点可用.

As many users of google CSE API, I received recently an email from "Google Custom Search" asking me "Please migrate to the Custom Search Element API 2.0". I checked the documentation, but they only describe how to integrate a google search input in a website. I am currently using the REST endpoint of google cse from a Node.js program, so I cannot use this. The documentation concerning the REST endpoint still references the V1, so I am a bit lost. I am wondering if this endpoint is also deprecated and will soon stop working, and if the v2 of the API is (or will be) available via a REST endpoint.

此主题已发布在 谷歌官方论坛，似乎很多人都担心这个，但目前谷歌没有答案，所以我在这里试试！

This subject has already been posted on official Google forums, it seems that many people worry about this, but for now there is no answer from google, so I'm trying this here !

谢谢

推荐答案

我终于找到了满意的答案，感谢 Google CSE 论坛上的 Josh Sloat.以下是他从 Google 支持人员那里得到的答案:在查看相关问题和来自 Google Enterprise Search 支持团队之一的反馈后.如果您使用 JSON API 来检索结果而不是使用自定义搜索元素 API 1.0/2.0 代码片段那么您将不会受到发送的关于将自定义搜索元素 API 1.0 迁移到 2.0 的通信的影响.".因此，REST API 似乎不受此更新的影响！

I finally found a satisfying answer, thanks to Josh Sloat on the Google CSE forum. Here is the answer he got from Google support : "Upon looking on a related issue and feedback from one of the Google Enterprise Search Support Team. If you are using JSON API to retrieve results and not using custom search element API 1.0/2.0 code snippets then you won't be impacted with the communication sent regarding the migration of custom search element API 1.0 to 2.0.". So it appears that the REST API isn't affected by this update !

这篇关于Google CSE REST API:不推荐使用 v1，是否有 v2?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！