hosting
PATCH /v1/sites/{siteId}/cdn/profile
Choose whether we keep the recommended CDN profile applied automatically.
Упълномощаване
Изпратете API ключ като токен за носене. Ключът трябва да притежава разрешението hosting.cdn.manage; ключ без него се отхвърля с 403, а не с 404.
Този ендпойнт не изисква идентификатор на организация. Вашият ключ вече идентифицира организацията, към която принадлежи, и отговорът е ограничен до нея.
Опитайте
Заменете всичко в квадратни скоби със собствени стойности, а ключовия заместващ символ – с ключ от вашето табло за управление.
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> }'Влязохте ли в профила си? API конзолата във вашето табло за управление попълва действителното идентификационно число на вашата организация и вашия собствен ключ и изпълнява заявката спрямо реалното API, за да можете да видите действителния отговор. Отворете този крайpoint в API конзолата
Детайли
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.
Параметри
| Име | Тип | Задължително | Какво представлява |
|---|---|---|---|
siteId (path) | Uuid | Да | Site ID (UUIDv7). |
Тяло на заявката
| Име | Тип | Задължително | Какво представлява |
|---|---|---|---|
managed | boolean | Да | true to have us keep the recommended profile applied; false to go back to reporting drift and changing nothing. |
Отговор
| Име | Тип | Задължително | Какво представлява |
|---|---|---|---|
site_id | Uuid | Да | UUIDv7 identifier — sortable by creation time (docs/02 §8). |
profile | string | Да | 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 | Да | Whether this site's CDN can express the profile's zone settings. |
cache_rules_supported | boolean | Да | 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[] | Да | 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… |
settings | SiteCdnProfileSetting[] | Да | — |
rules | SiteCdnProfileRule[] | Да | The recommended rules, in evaluation order. Bypasses come first. |
managed | boolean | Да | 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.… |
Грешки, които този крайpoint може да върне
401 · 403 · 404 · 422 · 429 · 502 · 503