Over the past few years, we’ve been updating our APIs with new versions across Drive and Calendar, as well as those used for managing Google Apps for Work domains. These new APIs offered developers several improvements over older versions of the API. With each of these introductions, we also announced the deprecation of a set of corresponding APIs.
As per previous reminders, the deprecation period for these APIs is coming to an end. As of April 20, 2015, we will discontinue these deprecated APIs. Calls to these APIs and any features in your application that depend on them will not work after April 20th.
When updating, we also recommend that you use the opportunity to switch to OAuth2 for authorization. Older protocols, such as ClientLogin, AuthSub, and OpenID 2.0, have also been deprecated and are scheduled to shut down on April 20, 2015.
In the coming weeks, we’ll be contacting domain administrators whose applications are still using these deprecated APIs with a final reminder email and guidance on specific migration paths.
*Note that since our last reminder, where we recommended the Email Migration API v2 as the replacement for the Email Migration API v1, the Gmail API has been announced as the replacement for both Email Migration APIs (v1 and v2).
Email Migration API v2 will be turned down on November 1, 2015, and we recommend starting the process of switching to the Gmail API. To aid you with this effort, we've put together this migration guide. For those who may have recently migrated from Email Migration API v1 (set to be turned down on April 20, 2015) to Email Migration API v2, note that the migration to Gmail API should require relatively minimal effort.
Release track:
Rapid release and Scheduled release
Note: all launches are applicable to all Google Apps editions unless otherwise noted
Launch release calendar
Get these product update alerts by email
Subscribe to the RSS feed of these updates
As per previous reminders, the deprecation period for these APIs is coming to an end. As of April 20, 2015, we will discontinue these deprecated APIs. Calls to these APIs and any features in your application that depend on them will not work after April 20th.
Discontinued API | Replacement API | |
No replacement available |
When updating, we also recommend that you use the opportunity to switch to OAuth2 for authorization. Older protocols, such as ClientLogin, AuthSub, and OpenID 2.0, have also been deprecated and are scheduled to shut down on April 20, 2015.
In the coming weeks, we’ll be contacting domain administrators whose applications are still using these deprecated APIs with a final reminder email and guidance on specific migration paths.
*Note that since our last reminder, where we recommended the Email Migration API v2 as the replacement for the Email Migration API v1, the Gmail API has been announced as the replacement for both Email Migration APIs (v1 and v2).
Email Migration API v2 will be turned down on November 1, 2015, and we recommend starting the process of switching to the Gmail API. To aid you with this effort, we've put together this migration guide. For those who may have recently migrated from Email Migration API v1 (set to be turned down on April 20, 2015) to Email Migration API v2, note that the migration to Gmail API should require relatively minimal effort.
Release track:
Rapid release and Scheduled release
Note: all launches are applicable to all Google Apps editions unless otherwise noted
Launch release calendar
Get these product update alerts by email
Subscribe to the RSS feed of these updates