hosting

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

Move a live site's CDN onto your own account, or back to ours.

Dhammaan hosting bixiyayaasha

Xaqiijinta aqoonsiga

U dir furaha API ah calaamad dusha ah (bearer token). Furaha waa inuu wataa ruqadda hosting.cdn.manage; furaha aan wadan waxaa loo diidayaa 403, ee ma aha 404.

Boggan ma qaato aqoonsiga ururka. Furahaagu wuxuu horay u aqoonsanayaa ururka uu ka tirsan yahay, jawaabtuna waxay ku kooban tahay halkaas.

Isku day

Ku beddel wax kasta oo ku dhex jira qeebaha xaglaha ah qiimayaashaada, sidoo kalena haystaaha furaha ku beddel fure ka dhex muuqda dashboordigaaga.

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> }'

Ma sign-garaysay? Qalabka API ee ku jira dashboard-kaagu wuxuu buuxiyaa aqoonsigaaga ururka ee dhabta ah iyo furahaaga gaarka ah, wuxuuna ku shaqeysiiyaa codsiga API-ga nool si aad u aragto jawaabta dhabta ah. Kani ka fur barta kontoroolka ee API

Details

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`.

Cabiraha

MagacaNoocLoo baahan yahayMaxay tahay
siteId (path)UuidHaaSite ID (UUIDv7).

Codsiga jidhkiisa

MagacaNoocLoo baahan yahayMaxay tahay
to_ownbooleanHaa`true` moves the site onto your own connected Cloudflare account; `false` returns it to Zinn®'s pool.
footprint_acknowledgedbooleanMayaRequired 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_targetstringMayaPresent ⇒ 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_labelstringMayaOptional free-text name for the CDN the customer runs themselves.

Jawaab

MagacaNoocLoo baahan yahayMaxay tahay
old_zone_removedbooleanMayaOnly 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…
nameserversstring[]MayaOnly 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_idUuidHaaUUIDv7 identifier — sortable by creation time (docs/02 §8).
product_linestringHaaThe site product line, which decides whether the CDN is managed.
managedbooleanHaaTrue on the footprint-free line, where the CDN is platform-owned footprint machinery the customer neither configures nor sees.
enabledbooleanHaa
tierCdnTierHaa`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…
providerobjectHaaDisplay 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…
accountCdnAccountHaaWhich 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_targetstringMayaWhere 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_labelstringMayaWhat 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_minorintegerHaaMonthly premium-tier price in integer minor units (§2.8).
currencystringHaaISO-4217 code the price_minor above is expressed in.
edgeCdnEdgeHaaWhich 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…

Cilladaha ay bartaani soo celin karto

401 · 403 · 404 · 422 · 429 · 503