hosting
PATCH /v1/sites/{siteId}/cdn/profile
Choose whether we keep the recommended CDN profile applied automatically.
Authentification
Envoyez une clé API en tant que jeton du porteur. La clé doit posséder l'autorisation hosting.cdn.manage ; une clé qui ne l'a pas est refusée avec le code 403, et non 404.
Cet endpoint ne prend aucun identifiant d'organisation. Votre clé identifie déjà l'organisation à laquelle elle appartient, et la réponse y est limitée.
Essayer
Remplacez tout ce qui se trouve entre crochets par vos propres valeurs, et le espace réservé à la clé par une clé de votre tableau de bord.
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> }'Connecté ? La console d'API de votre tableau de bord saisit votre véritable ID d'organisation ainsi que votre propre clé, et exécute la requête sur l'API de production afin que vous puissiez voir la réponse réelle. Ouvrir ce point de terminaison dans la console API
Détails
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`.
Paramètres
| Nom | Type | Obligatoire | Qu'est-ce que c'est |
|---|---|---|---|
siteId (path) | Uuid | Oui | Site ID (UUIDv7). |
Corps de la requête
| Nom | Type | Obligatoire | Qu'est-ce que c'est |
|---|---|---|---|
managed | boolean | Oui | `true` to have us keep the recommended profile applied; `false` to go back to reporting drift and changing nothing. |
Réponse
| Nom | Type | Obligatoire | Qu'est-ce que c'est |
|---|---|---|---|
site_id | Uuid | Oui | UUIDv7 identifier — sortable by creation time (docs/02 §8). |
profile | string | Oui | 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 | Oui | Whether this site's CDN can express the profile's zone settings. |
cache_rules_supported | boolean | Oui | 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[] | Oui | 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[] | Oui | — |
rules | SiteCdnProfileRule[] | Oui | The recommended rules, in evaluation order. Bypasses come first. |
managed | boolean | Oui | 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… |
Erreurs que cet point de terminaison peut renvoyer
401 · 403 · 404 · 422 · 429 · 503