otherContacts

• copyOtherContactToMyContactsGroup — 将“其他联系人”复制为用户“myContacts”组中的一个新联系人。对同一用户的变更请求应顺序发送，以避免延迟增加和失败。
• list — 列出所有“其他联系人”，即不在任何联系人组中的联系人。“其他联系人”通常是来自交互的自动创建的联系人。同步令牌在完全同步 7 天后过期。使用过期同步令牌的请求将收到一个错误，其中包含 google.rpc.ErrorInfo，原因为 "EXPIRED_SYNC_TOKEN"。如果发生此类错误，客户端应执行不带 sync_token 的完全同步请求。
• search — 提供经过身份验证的用户的其他联系人中与搜索查询匹配的联系人列表。查询匹配来自 OTHER_CONTACT 源的联系人的 names、emailAddresses 和 phoneNumbers 字段。重要提示：在搜索之前，客户端应发送一个带有空查询的预热请求以更新缓存。请参阅 https://developers.google.com/people/v1/other-contacts#search_the_users_other_contacts

people

• batchCreateContacts — 创建一批新联系人，并返回新创建联系人的 PersonResponses。对同一用户的变更请求应顺序发送，以避免延迟增加和失败。
• batchUpdateContacts — 更新一批联系人，并返回一个资源名称到已更新联系人的 PersonResponses 的映射。对同一用户的变更请求应顺序发送，以避免延迟增加和失败。
• createContact — 创建一个新联系人，并返回该联系人的人员资源。如果为联系人源的单例字段（如：* biographies * birthdays * genders * names）指定了多个字段，请求将返回 400 错误。对同一用户的变更请求应顺序发送，以避免延迟增加和失败。
• deleteContactPhoto — 删除联系人的照片。对同一用户的变更请求应顺序执行，以避免锁争用。
• get — 通过指定资源名称提供有关人员的信息。使用 people/me 表示经过身份验证的用户。如果未指定 'personFields'，请求将返回 400 错误。
• getBatchGet — 通过指定一组请求的资源名称，提供有关特定人员列表的信息。使用 people/me 表示经过身份验证的用户。如果未指定 'personFields'，请求将返回 400 错误。
• listDirectoryPeople — 提供经过身份验证的用户所在域目录中的域配置文件和域联系人列表。当指定 sync_token 时，自上次同步以来删除的资源将作为 PersonMetadata.deleted 设置为 true 的人员返回。当指定 page_token 或 sync_token 时，所有其他请求参数必须与首次调用匹配。对于同步请求，写入操作可能会有几分钟的传播延迟。增量同步不适用于读后写场景。
• searchContacts — 提供经过身份验证的用户的分组联系人中与搜索查询匹配的联系人列表。查询匹配来自 CONTACT 源的联系人的 names、nickNames、emailAddresses、phoneNumbers 和 organizations 字段。重要提示：在搜索之前，客户端应发送一个带有空查询的预热请求以更新缓存。请参阅 https://developers.google.com/people/v1/contacts#search_the_users_contacts
• searchDirectoryPeople — 提供经过身份验证的用户所在域目录中与搜索查询匹配的域配置文件和域联系人列表。
• updateContact — 更新现有联系人的联系人数据。任何非联系人数据将不会被修改。待更新人员中的任何非联系人数据将被忽略。update_mask 中指定的所有字段将被替换。如果未为要更新的联系人指定 person.metadata.sources 或者没有联系人源，服务器将返回 400 错误。
• updateContactPhoto — 更新联系人的照片。对同一用户的变更请求应顺序发送，以避免延迟增加和失败。
• connections — 对 'connections' 资源的操作

发现命令

在调用任何 API 方法之前，请先检查它：

# 浏览资源和方法
gws people --help

# 检查方法的必需参数、类型和默认值
gws schema people.<resource>.<method>

使用 gws schema 的输出构建你的 --params 和 --json 标志。

每周安装数

1

代码仓库

aurimasapg/cli

首次出现

1 天前

安全审计

Gen Agent Trust HubPassSocketPassSnykPass

安装于

amp1

cline1

opencode1

cursor1

kimi-cli1

codex1

otherContacts

• copyOtherContactToMyContactsGroup — Copies an "Other contact" to a new contact in the user's "myContacts" group Mutate requests for the same user should be sent sequentially to avoid increased latency and failures.
• list — List all "Other contacts", that is contacts that are not in a contact group. "Other contacts" are typically auto created contacts from interactions. Sync tokens expire 7 days after the full sync. A request with an expired sync token will get an error with an google.rpc.ErrorInfo with reason "EXPIRED_SYNC_TOKEN". In the case of such an error clients should make a full sync request without a sync_token.
• search — Provides a list of contacts in the authenticated user's other contacts that matches the search query. The query matches on a contact's names, emailAddresses, and phoneNumbers fields that are from the OTHER_CONTACT source. IMPORTANT : Before searching, clients should send a warmup request with an empty query to update the cache. See https://developers.google.com/people/v1/other-contacts#search_the_users_other_contacts

people

• batchCreateContacts — Create a batch of new contacts and return the PersonResponses for the newly Mutate requests for the same user should be sent sequentially to avoid increased latency and failures.
• batchUpdateContacts — Update a batch of contacts and return a map of resource names to PersonResponses for the updated contacts. Mutate requests for the same user should be sent sequentially to avoid increased latency and failures.
• createContact — Create a new contact and return the person resource for that contact. The request returns a 400 error if more than one field is specified on a field that is a singleton for contact sources: * biographies * birthdays * genders * names Mutate requests for the same user should be sent sequentially to avoid increased latency and failures.
• deleteContactPhoto — Delete a contact's photo. Mutate requests for the same user should be done sequentially to avoid // lock contention.
• get — Provides information about a person by specifying a resource name. Use people/me to indicate the authenticated user. The request returns a 400 error if 'personFields' is not specified.
• getBatchGet — Provides information about a list of specific people by specifying a list of requested resource names. Use people/me to indicate the authenticated user. The request returns a 400 error if 'personFields' is not specified.
• listDirectoryPeople — Provides a list of domain profiles and domain contacts in the authenticated user's domain directory. When the sync_token is specified, resources deleted since the last sync will be returned as a person with PersonMetadata.deleted set to true. When the page_token or sync_token is specified, all other request parameters must match the first call. Writes may have a propagation delay of several minutes for sync requests. Incremental syncs are not intended for read-after-write use cases.
• searchContacts — Provides a list of contacts in the authenticated user's grouped contacts that matches the search query. The query matches on a contact's names, nickNames, emailAddresses, phoneNumbers, and organizations fields that are from the CONTACT source. IMPORTANT : Before searching, clients should send a warmup request with an empty query to update the cache. See https://developers.google.com/people/v1/contacts#search_the_users_contacts
• searchDirectoryPeople — Provides a list of domain profiles and domain contacts in the authenticated user's domain directory that match the search query.
• updateContact — Update contact data for an existing contact person. Any non-contact data will not be modified. Any non-contact data in the person to update will be ignored. All fields specified in the update_mask will be replaced. The server returns a 400 error if person.metadata.sources is not specified for the contact to be updated or if there is no contact source.
• updateContactPhoto — Update a contact's photo. Mutate requests for the same user should be sent sequentially to avoid increased latency and failures.
• connections — Operations on the 'connections' resource

Discovering Commands

Before calling any API method, inspect it:

# Browse resources and methods
gws people --help

# Inspect a method's required params, types, and defaults
gws schema people.<resource>.<method>

Use gws schema output to build your --params and --json flags.

Weekly Installs

1

Repository

aurimasapg/cli

First Seen

1 day ago

Security Audits

Gen Agent Trust HubPassSocketPassSnykPass

Installed on

amp1

cline1

opencode1

cursor1

kimi-cli1

codex1