使用 https://spreadsheets.google.com/feeds/时是否需要迁移到 Drive API [英] Do you need to migrate to Drive API when using https://spreadsheets.google.com/feeds/

问题描述

1 月 22 日，我收到一封来自 Google Apps 的电子邮件，主题为重要提示:从已停用的 Documents List API 迁移的步骤".

The 22nd of January, I received an email with the subject 'Important: Steps to migrate from discontinued Documents List API' from Google Apps .

重要提示:从已停用的 Documents List API 迁移的步骤

Important: Steps to migrate from discontinued Documents List API

管理员您好，

我们最近沟通Documents List API 将于 2015 年 4 月 20 日停用.此更改意味着将不再支持对此 API 的服务调用，并且使用此 API 实现的任何 Google Apps 功能将不再起作用.

We recently communicated that Documents List API will be discontinued on April 20, 2015. This change means that service calls for this API will no longer be supported, and any Google Apps features that are implemented using this API will no longer function.

我们的记录表明您可能有一个使用 Documents List API 的应用程序，我们建议您迁移到 Drive API，它具有 可比功能，尽快.

Our records indicate that you may have an application that uses Documents List API, and we recommend that you migrate to Drive API, which has comparable functionality, as soon as possible.

这是你需要做的:

确定您是否有向这些请求发出请求的应用程序网址类型:

Determine if you have an application that makes requests to these types of URLs:

• https://docs.google.com/feeds/
• https://docs.googleusercontent.com/
• https://spreadsheets.google.com/feeds/

将应用程序迁移到 DriveAPI.如果您有问题关于迁移，请联系 Google Apps for Work 支持.

Migrate the applications to Drive API. If you have questions about migration, please contact Google Apps for Work Support.

此致 Google Apps for Work 团队敬上

Sincerely, The Google Apps for Work Team

我认为它表示应用程序使用 https://spreadsheets.google.com/feeds/应该迁移到新的 Drive API.但在新的 Drive API 中，也使用了这个 URL:https://developers.google.com/google-apps/spreadsheets/#sheets_api_urls_visibilities_and_projections

I think it says that applications using https://spreadsheets.google.com/feeds/ should migrate to the new Drive API. But in the new Drive API, this URL is used too: https://developers.google.com/google-apps/spreadsheets/#sheets_api_urls_visibilities_and_projections

电子邮件或 Drive API 文档中的 URL 是否存在拼写错误?还是这封电子邮件是说，当您确定您使用了这些 URL 中的任何一个时，您就没事了?

Is there a typo somewhere in the URL either in the email or Drive API documentation? Or is this email saying that when you determined you used any of these URL's you're OK?

PS:我在 Google 开了一个案例，但我担心回复晚，所以我在这里问.

推荐答案

简答是否.

Docslist API 将被停用，因为它已被 Drive API 取代.在电子表格 API 的情况下，没有替代 API(可能 - 可能有一天)，所以它仍然受支持.

The Docslist API is being discontinued because it has been replaced by the Drive API. In the case of the Spreadsheet API, there is no replacement API (yet - maybe one day), so it remains supported.

唯一的问题是，在某些时候，仅支持 OAuth 2 进行身份验证/授权，因此，如果您使用的是 OAuth 1 或 u/p，您还有一些工作要做.

The only gotcha is that at some point, only OAuth 2 will be supported for authentication/authorisation so if you're using OAuth 1 or u/p, you have some work to do.

这篇关于使用 https://spreadsheets.google.com/feeds/时是否需要迁移到 Drive API的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！