hosting

PUT /v1/sites/{siteId}/cdn/security

Change a site's CDN security and bot settings.

Све hosting крајње тачке

Сва документација за програмере →

Аутентификација

Пошаљите API кључ као bearer токен. Кључ мора имати дозволу hosting.cdn.manage; кључ без ње се одбија уз 403, а не 404.

Ова крајња тачка не прихвата id организације. Ваш кључ већ идентификује организацију којој припада, а одговор је ограничен на њу.

Испробајте

Замените све што је у угластим заградама сопственим вредностима, а чувар места кључа кључем са своје контролне табле.

curl -X PUT https://api.zinndigital.com/v1/sites/{siteId}/cdn/security \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{  }'

Пријављени сте? API конзола на вашој контролној табли попуњава ваш прави id организације и ваш сопствени кључ, и покреће захтев према живом API-ју како бисте могли да видите стварни одговор. Отворите ову крајњу тачку у API конзоли

Детаљи

A merge: only the fields present are changed. A full-object write would turn a customer's AI-crawler policy off every time they changed their security level. The body carries settings and nothing else — additionalProperties: false, for the reason PUT /v1/sites/{siteId}/cdn/settings gives: these are pooled CDN accounts and a Cloudflare zone resolves by name alone, so a body key named domain or zone_id must be refused rather than discarded. The result is read back from the provider rather than echoed, because the provider silently ignores a bot control a zone's plan does not include — "we asked" and "it changed" are different facts. Requires hosting.cdn.manage. Bot management is a sold entitlement (protection_tier). Turning bot_fight_mode on, or setting ai_bots_protection/crawler_protection to block or managed_challenge, needs a plan that includes it and otherwise answers a plan refusal naming the tier held and the tier needed. Three things are deliberately NOT gated. Turning any control off is free on every plan — a customer whose plan changed must always be able to reach the floor rather than be stranded with a setting they cannot undo. allow is an explicit relaxation, not protection, so it is free too. And security_level: under_attack is free on every plan, for ever: it is the emergency DDoS response, and refusing it to a customer under active attack because of their plan is not a product decision this platform will make. Bot Fight Mode is opt-in. The platform never switches it on, and it can challenge automated traffic a site depends on — uptime monitors, payment callbacks and some crawlers. Switching it on for a site the platform itself runs answers 422 before anything reaches the provider. Every field is zone-wide. A site on a shared preview address is served by a zone every other preview site uses, so a write for it answers 422 before anything reaches the provider.

Параметри

НазивТипОбавезноШта је ово
siteId (path)UuidДаSite ID (UUIDv7).

Тело захтева

НазивТипОбавезноШта је ово
security_levelCdnSecurityLevelНеThe provider's own security-level vocabulary, passed through. Not ordered the way it reads — essentially_off sits between off and low — so nothing may treat it as a…
bot_fight_modebooleanНе—
ai_bots_protectionCdnAiBotModeНеHow the edge treats AI crawlers. disabled leaves them alone. This is the control on the screen most able to cost a site traffic, in either direction: blocking AI answer engines…
crawler_protectionCdnCrawlerProtectionModeНеWhether the edge challenges ordinary crawlers. A two-value switch, not the four-mode AI-crawler vocabulary — the provider answers 400 for block, managed_challenge and…
always_use_httpsbooleanНе—
automatic_https_rewritesbooleanНе—
opportunistic_encryptionbooleanНе—
min_tls_versionCdnMinTlsVersionНеThe oldest TLS version the edge will negotiate. A string — 1.10 is not a version.

Одговор

НазивТипОбавезноШта је ово
site_idUuidДаUUIDv7 identifier — sortable by creation time (docs/02 §8).
supportedbooleanДаWhether the CDN serving this site can express these settings at all. false for a provider with no equivalent vocabulary; the other fields then carry defaults and a client should…
unreadablestring[]НеFields the CDN account's credential could not read, so their values here are defaults, not the zone's state. A client renders each listed control disabled and says it could not be…
protection_tierstringДаThe protection level this organisation's plan sells (protection_tier). Absent from a plan means the floor — every site with a CDN already has the provider's baseline protection…
bot_management_includedbooleanДаWhether that tier reaches bot management — enabling bot_fight_mode, or setting ai_bots_protection/crawler_protection to block or managed_challenge. Derived server-side…
security_levelCdnSecurityLevelДаThe provider's own security-level vocabulary, passed through. Not ordered the way it reads — essentially_off sits between off and low — so nothing may treat it as a…
bot_fight_modebooleanДаChallenge traffic the provider classifies as automated. Read from the provider's bot-management resource, not from a zone setting — the zone setting of that name does not exist.
ai_bots_protectionCdnAiBotModeДаHow the edge treats AI crawlers. disabled leaves them alone. This is the control on the screen most able to cost a site traffic, in either direction: blocking AI answer engines…
crawler_protectionCdnCrawlerProtectionModeДаWhether the edge challenges ordinary crawlers. A two-value switch, not the four-mode AI-crawler vocabulary — the provider answers 400 for block, managed_challenge and…
always_use_httpsbooleanДаRedirect every plain-HTTP request to HTTPS at the edge.
automatic_https_rewritesbooleanДаRewrite insecure sub-resource URLs in HTML to HTTPS where possible.
opportunistic_encryptionbooleanДаAdvertise HTTP/2 over TLS to clients that arrive over plain HTTP.
min_tls_versionCdnMinTlsVersionДаThe oldest TLS version the edge will negotiate. A string — 1.10 is not a version.

Грешке које ова крајња тачка може вратити

401 · 403 · 404 · 422 · 429 · 502 · 503