Tag Archives: API

Google Vault API updates to replace Team Drives fields

What’s changing 

We recently updated the Vault API to reflect the renaming of “Team Drives” to “shared drives.” You can see more details on the name change here.

The new fields in the API are detailed below. Currently, both the old and updated fields are available. However, we will stop supporting the old fields in the API on June 1, 2020. You will need to migrate any app(s) that use the affected fields before June 1, 2020, to make sure they continue to work.

The specific changes to the API are:


Who’s impacted 

Admins and developers only

Why you’d use it 

Google Vault is the eDiscovery and compliance solution for G Suite, allowing customers to retain, hold, search, and export their data. The API means you can programmatically manage your organization's eDiscovery operations. If you’ve developed apps that use the API, you may need to make minor updates to make sure they keep working as intended.

How to get started 




Helpful links 




Availability 

Rollout details 
  • New “shared drives” fields are available today.
  • We will stop supporting the old “Team Drives” related API fields on June 1, 2020.


G Suite editions
  • Google Vault is available to G Suite Business, Enterprise, Education, and Enterprise for Education editions, as well as other G Suite customers with the Vault add-on license.


Stay up to date with G Suite launches

Minor cleaning up in the Search Console API

With the move to the new Search Console, we've decided to clean up some parts of the Search Console API as well. In the Search Analytics API, going forward we'll no longer support these Android app search appearance types:

  • Is Install
  • Is App Universal
  • Is Opened

Since these appearance types are no longer used in the UI, they haven't been populated with data recently. Going forward, we won't be showing these types at all through the API. 

Additionally, for the Sitemaps API, we're no longer populating data on indexing status of submitted sitemap files in the "Indexed" field.

We're still committed to the Search Console API. In particular, we're working on updating the Search Console API to the new Search Console. We don't have any specific timeframes to share at the moment, but stay tuned to find out more!


Posted by Ziv Hodak, Search Console product manager

Take action by July 8, 2019, to ensure your users can continue to use third-party apps accessing Gmail data

What’s changing

Security and privacy are extremely important to Google. To better protect your data, we’ve made an important update to our policies governing third-party apps (web, Android, iOS, Chrome, and other apps) accessing Gmail data using G Suite APIs and OAuth2.

We previously announced that apps accessing user data for non-enterprise accounts using certain Gmail APIs had to be verified to ensure compliance with new privacy and security requirements using our OAuth API Application Verification. Starting on July 8, 2019, we’ll apply similar requirements for apps you may use within your domain.

Who’s impacted

Admins and end users

Why it matters

While existing unverified apps will continue to work for users who installed them before July 8, after this date we’ll block new installs for unverified third-party apps that access Gmail data and that you don’t explicitly trust (whitelist) in the G Suite Admin console.

How to get started


  • Admins:
    • Review unverified apps in your environment: Please review the unverified apps currently in use in your organization’s G Suite environment and decide which apps you want to trust and allow users to continue to install. The primary admin contact at your organization will receive an email by June 21, 2019, with a list of those unverified apps, including the number of users and whether or not you have trusted them in API Permissions.
    • Trust apps that you want to allow users to continue to install: To trust an app, use our API Permissions (OAuth apps whitelisting) feature in the Security section of the Admin console. Trusting an app also means that, if users consent, the app will have access to some G Suite user data (OAuth2 scopes) that you’ve otherwise restricted using this same tool. For example, if you’ve generally blocked access to Gmail OAuth2 scopes, trusted apps will have access for accounts where users consent.