GET /v1/sites/{siteId}/cdn/targets

身份验证

请将 API 密钥作为 bearer 令牌发送。该密钥必须具有 hosting.cdn.manage 权限；缺少该权限的密钥将被拒绝并返回 403 状态码，而非 404。

此端点不需要组织 ID。您的密钥已用于识别其所属的组织，且响应范围也仅限于该组织。

免费试用

将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。

curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/cdn/targets \
  -H "Authorization: Bearer zdk_live_…"

已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。 在 API 控制台中打开此端点

详细信息

Every destination this site's CDN could move to: Zinn®'s own pool, one row per CDN account you have connected, and passthrough (an edge you run yourself). ⛔⛔ This operation exists because a customer could not see their own accounts at all. A connected CDN account is a provider-account row scoped to your organisation, and until this endpoint the only route that read that table was a staff one — so a customer who connected two Cloudflare accounts could see neither, and the (now deprecated) switchSiteCdn's body was a boolean that cannot name one of two. The account you connect on the Connections page is listed too, as one own row. ⛔ An unusable target is LISTED, with its reason, never hidden. "My account is not in the list" and "my account is in the list and says the token was revoked" send you to two different places, and only the second is true. reason is a machine key so the client renders the sentence in your language. ⭐ changes_nameservers is the field to render before the customer clicks. A zone-owning CDN assigns nameservers per account, so a move between two accounts on the same vendor still changes the delegation your registrar must point at. Advisory and read-only: a target listed as available may still fail at swap time because a credential was revoked in between, and the swap says so. Requires hosting.cdn.manage.

参数

响应

此端点可能返回的错误

401 · 403 · 404 · 429