links
POST /v1/content/targets/probe
Re-check, for real, whether these sites can receive a post.
身份验证
请将 API 密钥作为 bearer 令牌发送。此端点在规范中未指明具体的权限,因此请为您的密钥赋予所需的最小权限,并通过检查响应来确认,而不是盲目假设。
此端点不需要组织 ID。您的密钥已用于识别其所属的组织,且响应范围也仅限于该组织。
免费试用
将尖括号中的内容替换为您自己的值,并将键占位符替换为您仪表板中的一个键。
curl -X POST https://api.zinndigital.com/v1/content/targets/probe \
-H "Authorization: Bearer zdk_live_…" \
-H "Content-Type: application/json" \
-d '{ "site_ids": <string[]> }'已登录?您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥,并针对实时 API 运行请求,以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
Contacts each named site's CMS and stores what came back. Gated on `links.edit`, because it makes outbound calls to the customer's own infrastructure. ⛔ Bounded at 100 sites per call and run 10 at a time. A refresh over a whole estate would be a self-inflicted outage; the picker refreshes what is on screen. ⛔ A site that could not be reached comes back `unknown`, never `unsuitable`, and a credential the CMS refused comes back with reason `no_credential` — the site is perfectly capable and we are the ones who cannot get in.
参数
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
requires (query) | string | 否 | The same comma-separated capability ids `listContentTargets` takes, so a client re-rendering rows from this response gets the same `missingCapabilities` it would get from a refe… |
请求正文
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
site_ids | string[] | 是 | — |
响应
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
checked | integer | 是 | — |
items | SiteTarget[] | 是 | — |
此端点可能返回的错误
401 · 403 · 422