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. Scopes previously requested by your apps may now be
deprecated or invalid. Developers should update their code to remove or update
references to Google+, Google+ APIs, and any related OAuth scopes.
With this change, scopes that have Google+ names and which are primarily related
to Sign-In, People APIs, or misnamed scopes unrelated to Google+ functionality
will continue to be recognized, though they will be mapped to their canonical
scope names. All other requested Google+ named scopes will be ignored.
You should update your app to only use the recommended scopes. For example,
when:
making OAuth requests
checking for scopes granted as a result of an authorization request
debugging a token using the tokeninfo endpoint
Apps that do not update to the latest scopes will experience the following
behavior:
Token request or token introspection
Behavior
Google+ named scopes that have a non-Google+ canonical scope
Request will succeed but the scopes associated with the token will be the canonical scope, not the Google+ named scope. If your app is checking the token for the presence of a Google+ named scope, your check may fail.
Google+ and non-Google+ scopes together
Request will succeed, but only non-Google+ scopes (after mapping to a possible canonical scope) will be contained in the token.
Google+ scopes with no replacement only
Error as there are no valid scopes contained in the request.
If you use software libraries or SDKs to access Google Account data we recommend
updating to the latest versions of the software when available. Please contact
your software provider to confirm software used by your website or application
is not impacted by the Google+ shutdown if you are unsure.
Please examine your site or app's code for impacted Google+ named scopes and
make changes as outlined below.
Identity scopes
Replace any base identity scopes specific to Google+ with their
OpenID Connect equivalents.
Deprecated Scope
Canonical scope
Recommended replacement scope
https://www.googleapis.com/auth/plus.me
openid
openid
https://www.googleapis.com/auth/plus.login
profile
profile
Information about a profile and people
Replace scopes requesting non-public profile data with the
People API equivalents.
[[["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 any associated scopes may now be deprecated or invalid.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers must update their code to remove or replace references to Google+, Google+ APIs, and outdated OAuth scopes.\u003c/p\u003e\n"],["\u003cp\u003eCertain Google+ named scopes related to Sign-In, People APIs, or misnamed scopes will be mapped to their new canonical scope names.\u003c/p\u003e\n"],["\u003cp\u003eApps that do not update their scopes may encounter errors, such as requests failing or receiving tokens without the expected Google+ scopes.\u003c/p\u003e\n"],["\u003cp\u003eSpecific Google+ scopes for functionalities like managing circles, media uploads, and reading/writing streams have no direct replacement and should be removed from the app.\u003c/p\u003e\n"]]],["Google+ APIs shut down on March 7, 2019, requiring developers to update their code. Apps must remove or update references to Google+ and its related OAuth scopes. Some Google+ named scopes will map to canonical scope names, while others will be ignored. Developers must update OAuth requests and token checks to use recommended scopes like `openid`, `profile`, `email`, `contacts` and others. Apps failing to update will encounter errors, including ignored Google+ scopes and request failures. Several deprecated scopes have no replacement.\n"],null,["# Google+ Scopes Shutdown\n\nLegacy Google+ APIs have been [shut down](/+/api-shutdown) as of\n**March 7, 2019**. Scopes previously requested by your apps may now be\ndeprecated or invalid. Developers should update their code to remove or update\nreferences to Google+, Google+ APIs, and any related OAuth scopes.\n\nWith this change, scopes that have Google+ names and which are primarily related\nto Sign-In, People APIs, or misnamed scopes unrelated to Google+ functionality\nwill continue to be recognized, though they will be mapped to their canonical\nscope names. All other requested Google+ named scopes will be ignored.\n\nYou should update your app to only use the recommended scopes. For example,\nwhen:\n\n- making OAuth requests\n- checking for scopes granted as a result of an authorization request\n- debugging a token using the tokeninfo endpoint\n\nApps that do not update to the latest scopes will experience the following\nbehavior:\n\n| Token request or token introspection | Behavior |\n|--------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Google+ named scopes that have a non-Google+ canonical scope | Request will succeed but the scopes associated with the token will be the canonical scope, not the Google+ named scope. If your app is checking the token for the presence of a Google+ named scope, your check may fail. |\n| Google+ and non-Google+ scopes together | Request will succeed, but only non-Google+ scopes (after mapping to a possible canonical scope) will be contained in the token. |\n| Google+ scopes with no replacement only | Error as there are no valid scopes contained in the request. |\n\nIf you use software libraries or SDKs to access Google Account data we recommend\nupdating to the latest versions of the software when available. Please contact\nyour software provider to confirm software used by your website or application\nis not impacted by the Google+ shutdown if you are unsure.\n\nPlease examine your site or app's code for impacted Google+ named scopes and\nmake changes as outlined below.\n\nIdentity scopes\n===============\n\nReplace any base identity scopes specific to Google+ with their\n[OpenID Connect](/identity/protocols/OpenIDConnect) equivalents.\n\n| Deprecated Scope | Canonical scope | Recommended replacement scope |\n|----------------------------------------------|-----------------|-------------------------------|\n| `https://www.googleapis.com/auth/plus.me` | `openid` | `openid` |\n| `https://www.googleapis.com/auth/plus.login` | `profile` | `profile` |\n\nInformation about a profile and people\n======================================\n\nReplace scopes requesting non-public profile data with the\n[People API](/people/v1/how-tos/authorizing#OAuth2Authorizing) equivalents.\n\n| Deprecated Scope | Canonical scope | Recommended replacement scope |\n|--------------------------------------------------------------|--------------------------------------------------------------|---------------------------------------------------------------------------------------------------|\n| `https://www.googleapis.com/auth/plus.profile.agerange.read` | `https://www.googleapis.com/auth/profile.agerange.read` | `https://www.googleapis.com/auth/profile.agerange.read` |\n| `https://www.googleapis.com/auth/plus.profile.emails.read` | `https://www.googleapis.com/auth/profile.emails.read` | `email` |\n| `https://www.googleapis.com/auth/plus.profile.language.read` | `https://www.googleapis.com/auth/profile.language.read` | `https://www.googleapis.com/auth/profile.language.read` |\n| `https://www.googleapis.com/auth/plus.peopleapi.readwrite` | `https://www.googleapis.com/auth/peopleapi.legacy.readwrite` | `https://www.googleapis.com/auth/contacts` or `https://www.googleapis.com/auth/contacts.readonly` |\n\nManage a business listing\n=========================\n\nReplace scopes used to manage business listings with the latest\n[Google My Business](/my-business) scope.\n\n| Deprecated Scope | Canonical scope | Recommended replacement scope |\n|--------------------------------------------------------|---------------------------------------------------|---------------------------------------------------|\n| `https://www.googleapis.com/auth/plus.business.manage` | `https://www.googleapis.com/auth/business.manage` | `https://www.googleapis.com/auth/business.manage` |\n\nScopes with no replacement\n==========================\n\nThe following scopes are specific to functionality provided by Google+ and have\nno replacement.\n\n| Deprecated Scope |\n|------------------------------------------------------|\n| `https://www.googleapis.com/auth/plus.circles.read` |\n| `https://www.googleapis.com/auth/plus.circles.write` |\n| `https://www.googleapis.com/auth/plus.media.upload` |\n| `https://www.googleapis.com/auth/plus.profiles.read` |\n| `https://www.googleapis.com/auth/plus.stream.read` |\n| `https://www.googleapis.com/auth/plus.stream.write` |"]]
