hosting
PATCH /v1/sites/{siteId}/cdn/profile
Choose whether we keep the recommended CDN profile applied automatically.
認証
ベアラー トークンとして API キーを送信します。キーには hosting.cdn.manage 権限が付与されている必要があります。権限のないキーは 404 ではなく 403 で拒否されます。
このエンドポイントは組織IDを受け付けません。お使いのキーによって所属する組織がすでに特定されており、レスポンスはその組織にスコープされます。
試してみる
アングルブラケット内のすべてをご自身の値に置き換え、キーのプレースホルダーをご利用中のダッシュボードのキーに置き換えてください。
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コンソールでは、実際の組織IDやお客様ご自身のキーが自動入力され、ライブAPIに対してリクエストが実行されるため、実際のレスポンスを確認することができます。 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 recomm… |
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. `t… |
このエンドポイントが返すエラー
401 · 403 · 404 · 422 · 429 · 503