身份验证
请将 API 密钥作为 bearer 令牌发送。该密钥必须具有 sites.view 权限；缺少该权限的密钥将被拒绝并返回 403 状态码，而非 404。
此端点不需要组织 ID。您的密钥已用于识别其所属的组织，且响应范围也仅限于该组织。
免费试用
将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。
curl -X GET https://api.zinndigital.com/v1/transfers \
-H "Authorization: Bearer zdk_live_…"已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
Both directions in one list. `direction` is computed per request from the caller's own organizations — the same row is `outgoing` to one party and `incoming` to the other, so a stored direction would be wrong for one of its two readers. `org_ids` carries the caller's own organization ids. That is the value a customer gives to somebody who is transferring them a site: transfers are addressed by organization id rather than by email address, because resolving a recipient by email would turn the offer form into a way to discover whether an address has an account with us and whether it is in arrears. Requires `sites.view`.
响应
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
transfers | SiteTransfer[] | 是 | — |
org_ids | Uuid[] | 是 | The caller's own organization ids — what they give to somebody transferring them a site. See `SiteTransferProposal.target_org_id` for why transfers are addressed this way. |
此端点可能返回的错误
401 · 403 · 429