hosting
PATCH /v1/sites/{siteId}/cdn/profile
Choose whether we keep the recommended CDN profile applied automatically.
Authenticatie
Stuur een API-sleutel mee als bearer token. De sleutel moet over de permissie hosting.cdn.manage beschikken; een sleutel zonder deze permissie wordt geweigerd met een 403 in plaats van een 404.
Dit eindpunt vereist geen organisatie-id. Uw sleutel identificeert al de organisatie waartoe deze behoort, en het antwoord is hierop afgestemd.
Probeer het
Vervang alles tussen punthaakjes door uw eigen waarden en de sleutelplaatsvervanger door een sleutel uit uw dashboard.
curl -X PATCH https://api.zinndigital.com/v1/sites/{siteId}/cdn/profile \
-H "Authorization: Bearer zdk_live_…" \
-H "Content-Type: application/json" \
-d '{ "managed": <boolean> }'Ingelogd? De API-console in je dashboard vult je echte organisatie-id en je eigen sleutel in, en voert het verzoek uit tegen de live API zodat je de daadwerkelijke respons kunt zien. Open dit eindpunt in de API-console
Details
Turns the *keep this applied* toggle on or off for one site. With it **off** — the default, and what every existing site has — a setting changed at the provider is reported as drift and only a human puts it back. With it **on**, the `zinn-managed-cdn-profile` sweep re-applies the recommendation on a cadence. The default is off on purpose and it matters most for a customer on their **own** provider account: silently correcting a value they changed deliberately, inside an account they pay for, is not something to opt anybody into. Setting the toggle **does not apply anything**. Arming an automation and writing to a zone are different acts, so a customer switching it on to see what it does has not thereby had their edge rewritten — the sweep picks it up on its next pass, and anyone who wants it now uses the `POST` above. A site that is not served through our CDN is a `404`. Requires `hosting.cdn.manage`.
Parameters
| Naam | Type | Verplicht | Wat dit is |
|---|---|---|---|
siteId (path) | Uuid | Ja | Site ID (UUIDv7). |
Aanvraaglichaam
| Naam | Type | Verplicht | Wat dit is |
|---|---|---|---|
managed | boolean | Ja | `true` to have us keep the recommended profile applied; `false` to go back to reporting drift and changing nothing. |
Reactie
| Naam | Type | Verplicht | Wat dit is |
|---|---|---|---|
site_id | Uuid | Ja | UUIDv7 identifier — sortable by creation time (docs/02 §8). |
profile | string | Ja | Which recommended profile applies to this site, chosen by product line — `footprint_free` caches HTML aggressively, `mainstream` leaves that decision to the origin. |
settings_supported | boolean | Ja | Whether this site's CDN can express the profile's zone settings. |
cache_rules_supported | boolean | Ja | Whether this site's CDN can express per-request cache rules. Separate from `settings_supported` because a provider may offer one and not the other. |
drifted | string[] | Ja | Setting keys whose live value differs from the recommendation, plus `cache_rules` when a recommended rule is missing at the provider. Empty means the zone matches what we recomm… |
settings | SiteCdnProfileSetting[] | Ja | — |
rules | SiteCdnProfileRule[] | Ja | The recommended rules, in evaluation order. Bypasses come first. |
managed | boolean | Ja | Whether the customer has asked us to keep this profile applied. `false` — the default — means drift is reported and nothing is corrected without a person pressing the button. `t… |
Fouten die dit eindpunt kan retourneren
401 · 403 · 404 · 422 · 429 · 503