hosting
POST /v1/sites/{siteId}/cdn/switch
Move a live site's CDN onto your own account, or back to ours.
المصادقة
أرسل مفتاح واجهة برمجة التطبيقات (API key) كرمز حامل (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
التفاصيل
Actually **moves** the site: creates the zone on the destination account, points the site at it, and removes the old one. ⛔ **`PUT /v1/sites/{siteId}/cdn` records a CHOICE; this performs it.** That endpoint writes the tier, the connection and the vendor and saves the row — it creates no zone, repoints nothing and removes nothing. Until this operation existed, selecting "your own CDN account" produced a tab that said so over a site still served entirely by a Zinn® pool zone, which was also still billing. Nothing failed: the row was exactly what had been asked for, and the world was untouched. **The order is the safety property.** The destination zone is created and read back first; the site is repointed second; the old zone is deleted last. Deleting first leaves a window in which the records name an edge that no longer exists — an outage the customer sees before we do. This order's failure mode is that the site is briefly reachable through two edges, which nobody notices. `old_zone_removed` in the response is an **observation, not an intention**: a destination that could not be reached fails the whole call with nothing changed, but a *source* that refuses the delete does not — the move has succeeded and the site is served correctly, while the customer is still being billed by the old provider and has to go and cancel it. That is why it is reported rather than assumed. ⛔ There is no origin, zone or account field. Every one is derived server-side from what the site is actually placed on: a caller-supplied origin is how an edge gets pointed at somebody else's server. 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_own | boolean | نعم | `true` moves the site onto your own connected Cloudflare account; `false` returns it to Zinn®'s pool. |
footprint_acknowledged | boolean | لا | 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 t… |
passthrough_target | string | لا | 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_label | string | لا | Optional free-text name for the CDN the customer runs themselves. |
الاستجابة
| الاسم | النوع | مطلوب | ما هو هذا |
|---|---|---|---|
old_zone_removed | boolean | لا | Only on a `switchSiteCdn` response: whether the site's **previous** zone was really deleted. ⛔ An observation, not an intention — a source account that refuses the delete does n… |
nameservers | string[] | لا | Only on a switch response, and only for a zone-owning CDN: the nameservers the destination zone is served from. ⛔ **The customer has to act on this.** Cloudflare assigns a names… |
site_id | Uuid | نعم | UUIDv7 identifier — sortable by creation time (docs/02 §8). |
product_line | string | نعم | The site product line, which decides whether the CDN is managed. |
managed | boolean | نعم | True on the footprint-free line, where the CDN is platform-owned footprint machinery the customer neither configures nor sees. |
enabled | boolean | نعم | — |
tier | CdnTier | نعم | `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. ⛔⛔ `pass… |
provider | object | نعم | 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 #9… |
account | CdnAccount | نعم | 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 a… |
passthrough_target | string | لا | 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**, wh… |
passthrough_label | string | لا | 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 rathe… |
price_minor | integer | نعم | Monthly premium-tier price in integer minor units (§2.8). |
currency | string | نعم | ISO-4217 code the price_minor above is expressed in. |
edge | CdnEdge | نعم | Which edge is **actually** in front of this site, and which of the CDN screen's controls will do anything. ⛔⛔ **`enabled` above is not the same question and the two disagree on… |
الأخطاء التي يمكن أن تُرجعها نقطة النهاية هذه
401 · 403 · 404 · 422 · 429 · 503