Stay organized with collections Save and categorize content based on your preferences.
The People API lets you:
For example, suppose that the authenticated user, Jen, has Fabian and Ranjith in her private contacts. When your app calls people.connections.list to read a list of her connections, Jen is presented with a consent screen asking to give the app access to the list. If Jen consents, the app reads a list containing person resources for Fabian and Ranjith.
If the app needs information for a specific person, it can then call people.get, passing in a resource name, to get the person resource for that person.
The app can also manage contacts by creating new contacts using people.createContact, update existing contacts it has read from people.connections.list using people.updateContact, and delete contacts using people.deleteContact.
Google Workspace users can also list their directory domain profiles and domain contacts using people.listDirectoryPeople or search them using people.searchDirectoryPeople.
The people information that the People API reads is merged from various sources, depending on the following conditions:
Understanding Merged Person DataThe data for a person is derived from one main source type. Data from other sources is merged with this data if the sources are connected through verified email addresses, phone numbers, or profile URLs. These are the ways a person may be composed:
Only contact based people can be modified by mutation endpoints. Profile and domain contact mutations are not supported.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-05-07 UTC.
[[["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 2025-05-07 UTC."],[[["The People API allows reading and managing the authenticated user's contacts, including private contacts and \"Other contacts\"."],["Users can access profile information for authenticated users and their contacts, including public Google profile data and, when permitted, Google Workspace domain profile data."],["The API facilitates managing contacts by creating, updating, and deleting contacts through specific endpoints."],["Google Workspace users can utilize the API to list and search domain profiles and domain contacts."],["The People API merges data from various sources like public profiles, private profiles, contacts, and domain information based on verified email addresses, phone numbers, or profile URLs."]]],["The People API enables reading and managing authenticated user contacts, \"Other contacts,\" and profile information, including domain profiles. Apps can list connections via `people.connections.list`, retrieve specific person data using `people.get`, create contacts with `people.createContact`, update contacts with `people.updateContact`, and delete contacts via `people.deleteContact`. Google Workspace users can access domain contacts using `people.listDirectoryPeople` or `people.searchDirectoryPeople`. The data is merged from sources like public profiles, domain data, and private information, depending on user consent and scopes granted.\n"]]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4