Legacy People API

Stay organized with collections Save and categorize content based on your preferences.

Overview

Before the Google+ API Shutdown on March 7, 2019, the people.get and people.getOpenIdConnect methods were available for requesting a person’s profile.

To avoid breaking existing integrations with these methods supporting sign-in, a new minimal implementation only returns basic fields necessary for that functionality, such as name and email address, if authorized by the user. The Legacy People API is where these methods will remain available for existing callers at the existing HTTP endpoints.

FAQ

What is the Legacy People API?

The Legacy People API serves a limited new implementation of the legacy Google+ API people.get and people.getOpenIdConnect methods necessary for maintaining sign-in functionality. It is available to existing callers of the original methods that haven't migrated to recommended replacements such as Google Sign-in or Google People API at the time of the Google+ API shutdown.

Why is the Legacy People API enabled for my developer project?

For backward compatibility, the Legacy People API was automatically enabled for callers of the legacy Google+ API people.get and people.getOpenIdConnect methods based on continued traffic to those methods. Note that you can't manually enable the Legacy People API for any new developer projects.

What happens if I disable the Legacy People API?

Calls to the legacy people.get and people.getOpenIdConnect methods will start to be rejected with the response 403 FORBIDDEN.

Should I continue to use the Legacy People API?

We strongly recommend that you migrate from the legacy people.get and people.getOpenIdConnect methods to replacements such as Google Sign-in or Google People API as soon as possible. The Legacy People API will remain available for existing callers, but will have limited support going forward.

Can I enable the Legacy People API for a new developer project?

No, the Legacy People API cannot be enabled for new developer projects. Use recommended alternatives such as Google Sign-in or Google People API.

Is detailed documentation or example usage available for the Legacy People API?

The Legacy People API only prevents breakage of basic sign-in functionality for existing traffic. We strongly recommend that you migrate to replacements such as Google Sign-in or Google People API as soon as possible.