hosting

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

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

כל נקודות הקצה מסוג hosting

כל תיעוד המפתחים

אימות

שלחו מפתח API כאסימון נושא (bearer token). על המפתח לכלול את הרשאה hosting.cdn.manage; מפתח שאינו כולל אותה יידחה בסטטוס 403, ולא 404.

נקודת קצה זו אינה דורשת מזהה ארגון. המפתח שלך כבר מזהה את הארגון שאליו הוא שייך, והתגובה מוגבלת אליו בלבד.

נסה זאת

החלף כל דבר בסוגריים זוויתיים בערכים משלך, ואת מציין מיקום המפתח במפתח מלוח הבקרה שלך.

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 בלוח הבקרה שלך מזינה את מזהה הארגון האמיתי שלך ואת המפתח שלך, ומריצה את הבקשה מול ה-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