Back to Details

sent-contacts

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Sent Contacts

Sent联系人

Operate contacts with 
contacts.list
, 
contacts.get
, 
contacts.create_many
, 
contacts.delete
, and 
contacts.message_summary
.
使用
contacts.list
、
contacts.get
、
contacts.create_many
、
contacts.delete
和
contacts.message_summary
操作联系人。

Establish connection and scope

建立连接与权限范围

Use client-managed OAuth 2.1/PKCE. Never request or expose a token, API key, authorization header, client ID, or secret. Before a mutation, surface the active organization and Sender Profile from the connection context; if either is unavailable, use 
sent-account-readiness
to inspect the authorized scope. Reauthorize in the client to change scope.
Mask phone numbers where practical. Return only the contact fields needed for the task, and do not repeat contact data after it has been reviewed. Number presence or messaging history does not establish consent.
使用客户端管理的OAuth 2.1/PKCE。切勿请求或暴露令牌、API密钥、授权标头、客户端ID或密钥。执行变更操作前，从连接上下文显示当前组织和发送者配置文件；若其中任一不可用，使用
sent-account-readiness
检查授权权限范围。如需更改权限范围，请在客户端重新授权。
尽可能屏蔽电话号码。仅返回任务所需的联系字段，且在数据审核通过后不再重复显示联系人数据。号码存在或消息记录不代表已获得同意。

Read contacts

读取联系人

  • Use 
    contacts.list
    to search or page through contacts. Apply the narrowest available filter and do not dump an entire contact book unnecessarily.
  • Use 
    contacts.get
    when an exact contact identifier is known or before a delete.
  • Use 
    contacts.message_summary
    for the contact's messaging summary. Distinguish summary data from proof of consent or current reachability.
Read-only calls do not require mutation confirmation.
  • 使用
    contacts.list
    搜索或分页查看联系人。应用最严格的可用筛选条件，避免不必要地导出整个通讯录。
  • 当已知确切联系人标识符或在删除操作前，使用
    contacts.get
    。
  • 使用
    contacts.message_summary
    获取联系人的消息汇总。注意区分汇总数据与同意证明或当前可达性证明。
只读调用无需变更确认。

Create contacts in bulk

批量创建联系人

  1. Validate and deduplicate the proposed records locally. Preserve only fields the user actually supplied.
  2. Build the exact 
    contacts.create_many
    arguments without calling the tool.
  3. Show a payload preview with the selected organization, Sender Profile, record count, duplicate handling, and each exact target. Mask phone numbers where the operator can still verify them; reveal full values once only when exact verification requires it.
  4. Ask for explicit confirmation for this exact batch. Earlier or general approval is not sufficient.
  5. Call 
    contacts.create_many
    immediately after confirmation. Any change to the records or scope invalidates confirmation.
Never call 
contacts.create_many
without a preview and explicit confirmation immediately before the call. Treat every retry as a new mutation with a fresh preview and new explicit confirmation.
  1. 在本地验证并去重拟创建的记录。仅保留用户实际提供的字段。
  2. 构建准确的
    contacts.create_many
    参数，无需调用工具。
  3. 展示负载预览，包含所选组织、发送者配置文件、记录数量、重复项处理方式以及每个确切目标。在操作员仍可验证的情况下屏蔽电话号码；仅在需要确切验证时才一次性显示完整号码。
  4. 请求对此确切批次的明确确认。此前的一般性批准无效。
  5. 确认后立即调用
    contacts.create_many
    。记录或权限范围的任何变更都会使确认失效。
切勿在未展示预览且未获取即时明确确认的情况下调用
contacts.create_many
。将每次重试视为新的变更操作，需重新展示预览并获取新的明确确认。

Delete a contact

删除联系人

  1. Resolve the requested contact to one unambiguous identifier.
  2. Fetch the exact target first with 
    contacts.get
    . Never delete from a guessed identifier, broad filter, or stale list result.
  3. Show a delete preview containing the selected organization, Sender Profile, exact contact identifier, display label, and masked address. State that deletion is destructive.
  4. Ask for explicit confirmation to delete that exact target.
  5. Call 
    contacts.delete
    immediately after confirmation. If the target, scope, or record changes, fetch it again and repeat the preview.
Never call 
contacts.delete
without fetching the target and obtaining explicit confirmation immediately before the call. Every retry requires another fetch, a fresh preview, and new explicit confirmation.
  1. 将请求的联系人解析为唯一明确的标识符。
  2. 先使用
    contacts.get
    获取确切目标。切勿根据猜测的标识符、宽泛的筛选条件或过时的列表结果进行删除。
  3. 展示删除预览，包含所选组织、发送者配置文件、确切联系人标识符、显示标签和屏蔽后的地址。说明删除操作具有破坏性。
  4. 请求删除该确切目标的明确确认。
  5. 确认后立即调用
    contacts.delete
    。若目标、权限范围或记录发生变更，请重新获取目标并重复预览步骤。
切勿在未获取目标且未获取即时明确确认的情况下调用
contacts.delete
。每次重试都需要重新获取目标、展示新预览并获取新的明确确认。

Report results

报告结果

Report counts and stable identifiers, not full contact records. If a create or delete outcome is ambiguous, do not assume success and do not retry automatically. Re-read the exact target when possible, explain the uncertainty, and require a new confirmation before any further mutation.
报告数量和稳定标识符，而非完整联系人记录。若创建或删除结果不明确，请勿假设操作成功，也不要自动重试。尽可能重新读取确切目标，说明不确定性，并在进行任何进一步变更前要求新的确认。