Legacy Google+ APIs have been shut down as of March 7, 2019. Changes to the shutdown plan have been made recently which may mitigate its effect on some developers. Learn more.
Google+ integrations for web and mobile apps have also stopped functioning as of March 7, 2019. Learn more.
Google+ API Shutdown
Stay organized with collections
Save and categorize content based on your preferences.
Page Summary
Legacy Google+ APIs, including REST, Web, Android SDK, Domains, and Pages APIs, were shut down as of March 7, 2019.
Developers are strongly advised to remove all dependencies on Google+ APIs from their applications to avoid breakage and to migrate to alternative systems like Google Sign-in and Google People API.
Google has implemented new versions of several people.get and people.getOpenIdConnect APIs that return basic sign-in fields, and existing calls to these APIs will be automatically served by the new implementation for a period.
Google+ Sign-in is deprecated, but scopes required for it will now be remapped to existing Google Sign-in scopes to allow legacy applications to continue functioning temporarily until migration.
While consumer Google+ is being sunset, Google is investing in Google+ for enterprise organizations with new features and a new look.
UPDATES
February 28: This posting was updated with important, recent
changes to aspects of the shutdown covering Google+ Sign-in, Google+ APIs,
and Google+ OAuth scope requests. These changes may help mitigate the impact
of the shutdown for some developers.
January 29: A clarification regarding “plus.me” scope was
provided.
January 15: This posting was updated with new information
about OAuth scopes.
Legacy Google+ APIs have been shut down as of March 7, 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:
Google+ REST API
Google+ Web API
Google+ Android SDK
Google+ Domains API
Google+ Pages API
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:
The Google+ Sign-in feature has been fully deprecated.
Developers should migrate to
the more comprehensive Google Sign-in authentication system.
Over the Air Installs is now deprecated and has
been shut down.
To help mitigate the impact of the shutdown, we have made the following
changes to aspects of the Google+ APIs shutdown.
We have created a new implementation of several people.get and
people.getOpenIdConnect APIs that will only return basic fields necessary
for sign-in functionality such as name and email address, if authorized by
the user. The new implementation only allows an app to retrieve the profile
of the signed-in user, and can return only basic profile fields necessary
for user sign-in functionality.
While we still recommend that developers migrate to alternative APIs such as
Google Sign-in and
Google People API, for cases where
developers are unable to move over before March 7th, existing calls made to
the legacy Google+ people.get and people.getOpenIdConnect APIs will
automatically be served by this new implementation at the same HTTP endpoints
as before.
Likewise, requests for some OAuth scopes will no longer fail as previously
communicated. In most cases scope requests such as those used for sign in and
usage not related to Google+ will no longer return an error. However, other
scopes that authorized access to Google+ data such as Circle and Stream
information will still no longer be granted. See full outline of scope
behavior here.
While we strongly encourage developers to
migrate to the more
comprehensive Google Sign-in authentication system, for cases
where developers are unable to move over before March 7th, scopes required for
Google+ sign-in will now be remapped to existing
Google Sign-in (not Google+) scopes, which should allow these
legacy applications to continue to use Google+ Sign-in until they can migrate.
We are working with third party developers to help manage the transition and
may implement additional mitigations in limited cases where the issue would
impact hundreds of thousands of users. For example, we may allow temporary
access to legacy Google+ APIs for broken, non-social apps that are using the
API primarily for sign-in purposes.
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
have also been 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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-03-07 UTC."],[],["Legacy Google+ APIs shut down on March 7, 2019. Developers should remove dependencies on these APIs, including Google+ REST, Web, Android, Domains, and Pages APIs. Google+ Sign-in was deprecated in favor of Google Sign-in. New implementations of people.get and people.getOpenIdConnect APIs now only return basic sign-in data. Scope requests not tied to Google+ will succeed; others will not. Existing Google+ sign-in scopes will be remapped to Google Sign-in scopes. Temporary access to legacy APIs is possible in limited cases.\n"]]
