身份验证
请将 API 密钥作为 bearer 令牌发送。该密钥必须具有 sites.create 权限；缺少该权限的密钥将被拒绝并返回 403 状态码，而非 404。
此端点不需要组织 ID。您的密钥已用于识别其所属的组织，且响应范围也仅限于该组织。
免费试用
将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。
curl -X GET https://api.zinndigital.com/v1/cdn/targets \
-H "Authorization: Bearer zdk_live_…"已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
The CDN destinations a site you are about to create could be placed on: Zinn®'s own pool, and one row per CDN account you have connected. ⛔⛤ This exists because the create wizard asked a boolean. "Use my own CDN" is a checkbox, and a checkbox cannot name one of two accounts — so a customer with two Cloudflare accounts said "mine" and the platform chose which. The wizard also showed that checkbox only when a connected provider was literally cloudflare, so an account on Bunny or CDN77 had no control at all and no explanation for its absence. ⛔ Pass product_line. It is the one input that changes the answer: on a platform-managed line (Footprint-Free) creating straight onto your own account is refused — every site on one account can be linked to every other on it, which is what that line is sold to prevent — so each account comes back listed, unavailable, with reason: line_is_platform_managed. Listing it and saying why is the point: a customer who cannot find their account concludes the connection failed. ⭐ changes_nameservers is the field to render before the customer commits. A zone-owning CDN assigns nameservers per account, so choosing your own account means your registrar must be pointed at that account's pair. Advisory and read-only; the create itself re-checks everything. Requires sites.create.
参数
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
product_line (query) | string | 否 | The line the site will be created on, as the engine spells it (footprint_free, mainstream). Omitted means unmanaged, which is the permissive answer — the create re-checks, so… |
响应
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
data | CdnTarget[] | 是 | — |
此端点可能返回的错误
401 · 403 · 429