hosting

POST /v1/sites/{siteId}/cdn/switch

Deprecated: start a move of this site's CDN (use startSiteCdnSwap).

すべての hosting エンドポイント

すべての開発者向けドキュメント

認証

ベアラー トークンとして API キーを送信します。キーには hosting.cdn.manage 権限が付与されている必要があります。権限のないキーは 404 ではなく 403 で拒否されます。

このエンドポイントは組織IDを受け付けません。お使いのキーによって所属する組織がすでに特定されており、レスポンスはその組織にスコープされます。

試してみる

アングルブラケット内のすべてをご自身の値に置き換え、キーのプレースホルダーをご利用中のダッシュボードのキーに置き換えてください。

curl -X POST https://api.zinndigital.com/v1/sites/{siteId}/cdn/switch \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "to_own": <boolean> }'

ログインしていますか?ダッシュボード内のAPIコンソールでは、実際の組織IDやお客様ご自身のキーが自動入力され、ライブAPIに対してリクエストが実行されるため、実際のレスポンスを確認することができます。 API コンソールでこのエンドポイントを開く

詳細

Deprecated since 2026-09-11; stops answering on 2027-03-11. Use startSiteCdnSwap (POST /v1/sites/{siteId}/cdn/swap), which names the destination account. Every response carries Deprecation, Sunset and a Link to the successor. ⛔⛔ This operation no longer moves the site inside the request, and that is the fix, not a regression (D23680). It used to create the zone on the destination, repoint the site and delete the old zone in one call. On a zone-owning CDN the nameservers belong to the ACCOUNT, so your registrar still pointed at the old zone when it was deleted — the site went dark and the response said 200 with old_zone_removed: true. It now starts the same durable move as startSiteCdnSwap: the old zone is removed only once your domain is observed answering from the new nameservers, and every failure leaves the site serving where it was. The response shape is unchangedCdnConfig, 200 — and says only what is true the moment the move starts: the configuration is still the source's, old_zone_removed is false and nameservers is empty (the destination zone does not exist yet). swap is the move itself; poll getSiteCdnSwap for its progress and for the nameservers to set at your registrar. {"to_own": true} means your one usable CDN account. With more than one connected it is refused with a sentence naming startSiteCdnSwap, rather than guessed. A request for where the site already is answers 200 with swap: null and starts nothing. ⛔ There is no origin, zone or account field: every one is derived server-side from what the site is placed on. A Footprint-Free site needs footprint_acknowledged to move onto its own account (owner ruling G-3) and needs nothing to move back. Requires hosting.cdn.manage.

パラメータ

名前タイプ必須これがその内容です
siteId (path)UuidはいSite ID (UUIDv7).

リクエスト本文

名前タイプ必須これがその内容です
to_ownbooleanはいtrue moves the site onto your own connected Cloudflare account; false returns it to Zinn®'s pool.
footprint_acknowledgedbooleanいいえRequired to move a Footprint-Free site onto your own account (owner ruling G-3): every site on that account can be linked to every other one on it, which is the connection the…
passthrough_targetstringいいえPresent ⇒ move this site to passthrough (⚖️ ruling AB-5): publish this edge hostname as the domain's answer and remove our zone. Absent ⇒ to_own decides, exactly as before.…
passthrough_labelstringいいえOptional free-text name for the CDN the customer runs themselves.

返信

名前タイプ必須これがその内容です
old_zone_removedbooleanいいえOnly on a switchSiteCdn response, and always false there since that operation began starting a durable move (W43-06): nothing has been removed when the request answers.…
swapCdnSwap | nullいいえOnly on a switchSiteCdn response: the move that request started, or null when the site was already where it asked and nothing was started. Poll getSiteCdnSwap for its…
nameserversstring[]いいえOnly on a switch response, and always empty there now: the destination zone does not exist when the request answers. The nameservers to set at your registrar are…
site_idUuidはいUUIDv7 identifier — sortable by creation time (docs/02 §8).
product_linestringはいThe site product line, which decides whether the CDN is managed.
managedbooleanはいTrue on the footprint-free line, where the CDN is platform-owned footprint machinery the customer neither configures nor sees.
enabledbooleanはい
tierCdnTierはいbyo runs the site CDN on a CDN account the customer has connected — we hold the credential and drive it, so purge, TLS and zone state all work from the dashboard. ⛔⛔…
providerobjectはいDisplay name of the active CDN, or null when managed is true — naming the CDN in front of a footprint-free site would leak the footprint the line exists to hide (register…
accountCdnAccountはいWhich CDN account serves this site, and whether its credential still works. ⛔ Always present — never omitted for "we do not know", because an absent object is read by a client as…
passthrough_targetstringいいえWhere a passthrough site's traffic is pointed — the edge hostname the customer's own CDN gave them, which we publish as this domain's answer. Empty on every other tier,…
passthrough_labelstringいいえWhat the customer calls the CDN they run themselves. ⚠️ Unverified — we hold no credential for that edge, so this is their claim and a client must present it as theirs rather…
zone_nameserversstring[]いいえThe nameservers the CDN provider assigned this site's zone — Cloudflare issues a pair per zone — stored when the zone was created. This is what the domain must be delegated to for…
price_minorintegerはいMonthly premium-tier price in integer minor units (§2.8).
currencystringはいISO-4217 code the price_minor above is expressed in.
edgeCdnEdgeはいWhich edge is actually in front of this site, and which of the CDN screen's controls will do anything. ⛔⛔…

このエンドポイントが返すエラー

401 · 403 · 404 · 409 · 422 · 429 · 503