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.
Stay organized with collections
Save and categorize content based on your preferences.
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."],[[["\u003cp\u003eLegacy Google+ APIs were shut down on March 7, 2019, and developers should remove any dependencies on these APIs from their applications.\u003c/p\u003e\n"],["\u003cp\u003eNew implementations of the people.get and people.getOpenIdConnect APIs are available, returning only basic user information required for sign-in functionality.\u003c/p\u003e\n"],["\u003cp\u003eWhile it is recommended to migrate to alternative APIs such as Google Sign-in and Google People API, existing calls to the legacy Google+ people.get and people.getOpenIdConnect APIs will now be served by the new implementations.\u003c/p\u003e\n"],["\u003cp\u003eGoogle+ Sign-in has been deprecated, and developers should migrate to the more comprehensive Google Sign-in authentication system, with legacy Google+ sign-in scopes remapped to existing Google Sign-in scopes to support continued functionality for the time being.\u003c/p\u003e\n"],["\u003cp\u003eSpecific OAuth scope requests will no longer return an error unless it was for accessing Google+ data such as Circle or Stream information.\u003c/p\u003e\n"]]],["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"],null,["| **UPDATES**\n|\n|\n| **February 28:** This posting was updated with important, recent\n| changes to aspects of the shutdown covering Google+ Sign-in, Google+ APIs,\n| and Google+ OAuth scope requests. These changes may help mitigate the impact\n| of the shutdown for some developers.\n|\n|\n| **January 29:** A clarification regarding \"plus.me\" scope was\n| provided.\n|\n|\n| **January 15:** This posting was updated with new information\n| about OAuth scopes.\n\nLegacy Google+ APIs have been shut down as of **March 7, 2019**.\n\nDevelopers should have received one or more emails listing recently used\nGoogle+ API methods in their projects. Whether or not an email was received, we\nstrongly encourage developers to search for and remove any affected dependencies\non Google+ APIs from their applications.\n\nThe most commonly used Google+ legacy APIs that are being shut down include:\n\n- Google+ REST API\n- Google+ Web API\n- Google+ Android SDK\n- Google+ Domains API\n- Google+ Pages API\n\nNote that we have built new implementations for several people.get and\npeople.getOpenIdConnect APIs that are documented as belonging to the legacy\nGoogle+ APIs, including those listed above. The new implementations will only\nreturn basic fields necessary for sign-in functionality. More information can be\nfound below.\n\nAs previously announced, as part of these changes:\n\n- The Google+ Sign-in feature has been fully deprecated. Developers should [migrate](/identity/sign-in/web/quick-migration-guide) to the more comprehensive [Google Sign-in](/identity) authentication system.\n- Over the Air Installs is now deprecated and has been shut down.\n\n**To help mitigate the impact of the shutdown, we have made the following\nchanges to aspects of the Google+ APIs shutdown.**\n\n- 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.\n- While we still recommend that developers migrate to alternative APIs such as [Google Sign-in](/identity) and [Google People API](/people/api/rest/v1/people/get), 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.\n- 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](/+/scopes-shutdown).\n- While we strongly encourage developers to [migrate](/identity/sign-in/web/quick-migration-guide) to the more comprehensive [Google Sign-in](/identity) 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](/identity) (not Google+) scopes, which should allow these legacy applications to continue to use Google+ Sign-in until they can migrate.\n- 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.\n\nDevelopers should still remove any dependencies on Google+ APIs from their\napplications as failure to do so will most likely break their applications.\nDevelopers may consider alternative APIs such as [Google Sign-in](/identity)\nand [Google People API](/people/api/rest/v1/people/get) for their needs.\n\nGoogle+ integrations for web or mobile apps\nhave also been shut down. Please see this\n[additional notice](/+/integrations-shutdown).\n\nWhile we're sunsetting Google+ for consumers, we're investing in Google+ for\nenterprise organizations. They can expect a new look and new features -- more\ninformation is available in our [blog post](https://cloud.google.com/blog/products/g-suite/new-enterprise-grade-features-in-googleplus-help-businesses-drive-collaboration)."]]