links
GET /v1/content/link-sets
Your reusable link sets — the URLs you build links to, and the words for each.
身份验证
请将 API 密钥作为 bearer 令牌发送。此端点在规范中未指明具体的权限，因此请为您的密钥赋予所需的最小权限，并通过检查响应来确认，而不是盲目假设。
您的组织 ID 应填在此处
此端点将 org_id 作为查询参数。不填则调用涵盖您的整个租户子树；发送该参数则将调用范围缩小到一个组织。
您的组织ID位于控制面板的API密钥屏幕上，就在密钥本身的旁边。这是您在每次调用时使用的相同ID。
免费试用
将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。
curl -X GET https://api.zinndigital.com/v1/content/link-sets \
-H "Authorization: Bearer zdk_live_…"已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
A link set is a named list of destinations and, for each one, every anchor text you want used for it. Recipes point at a set rather than carrying their own copy, so a URL that changes changes in one place. Gated on `links.view`. Each row carries a `distribution`: the resolved share of every (URL, wording) pair, summing to 100. That is computed by the **same** function a recipe run uses, so the preview on screen and the links actually placed cannot disagree. When the shares cannot be resolved, `distribution` is empty and `distribution_error` says why — the two are separate fields because an empty list also means "this set has no links", and one value for two facts is not an answer.
参数
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
org_id (query) | string | 否 | — |
include_archived (query) | boolean | 否 | — |
响应
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
items | LinkSet[] | 是 | — |
total | integer | 是 | — |
此端点可能返回的错误
401 · 403