Update: This posting was updated on February 28, 2019 with important, recent changes to aspects of the shutdown covering Google+ Sign-in, Google+ APIs, and Google+ OAuth scope requests.
On March 7, 2019, we are shutting down the legacy Google+ APIs. This has been a progressive shutdown where calls to affected APIs began intermittently failing on January 28, 2019.
Developers should have received one or more emails listing recently used Google+ API methods in their projects. Whether or not an email was received, we strongly encourage developers to search for and remove any affected dependencies on Google+ APIs from their applications.
The most commonly used Google+ legacy APIs that are being shut down include:
Note that we have built new implementations for several people.get and people.getOpenIdConnect APIs that are documented as belonging to the legacy Google+ APIs, including those listed above. The new implementations will only return basic fields necessary for sign-in functionality. More information can be found below.
As previously announced, as part of these changes:
To help mitigate the impact of the shut down, we have made the following changes to aspects of the Google+ APIs shutdown.
Developers should still remove any dependencies on Google+ APIs from their applications as failure to do so will most likely break their applications. Developers may consider alternative APIs such as Google Sign-in and Google People API for their needs.
Google+ integrations for web or mobile apps are also being shut down. Please see this additional notice.
While we're sunsetting Google+ for consumers, we're investing in Google+ for enterprise organizations. They can expect a new look and new features -- more information is available in our blog post.
