hosting

PUT /v1/sites/{siteId}/wordpress/update-policy

Set the site's auto-update policy and apply it to WordPress.

Tüm hosting uç noktaları

Tüm geliştirici belgeleri

Kimlik Doğrulama

Bearer token olarak bir API anahtarı gönderin. Anahtar sites.view iznine sahip olmalıdır; bu izne sahip olmayan bir anahtar 404 ile değil, 403 ile reddedilir.

Bu uç nokta hiçbir organizasyon kimliği almaz. Anahtarınız zaten ait olduğu organizasyonu tanımlar ve yanıt bu organizasyonla sınırlandırılır.

Dene

Köşeli parantez içindeki her şeyi kendi değerlerinizle ve anahtar yer tutucusunu panonuzdan bir anahtarla değiştirin.

curl -X PUT https://api.zinndigital.com/v1/sites/{siteId}/wordpress/update-policy \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "core": <string<off, minor, all>>, "plugins": <boolean>, "themes": <boolean>, "ring": <string<canary, early, general>> }'

Oturum açtınız mı? Panonuzdaki API konsolu, gerçek organizasyon kimliğinizi ve kendi anahtarınızı otomatik olarak doldurur ve isteği canlı API üzerinde çalıştırarak gerçek yanıtı görmenizi sağlar. Bu uç noktayı API konsolunda açın

Ayrıntılar

Stores the policy and writes it to the site in the same call, then re-reads the site and returns what it found. ⛔ Storing without applying is the defect this endpoint exists to avoid: a stored row saying core: off over a WordPress that is still updating itself is worse than no row, because the screen then says the operator's decision took effect. The response body is a fresh read, never an echo of the request. ⛔ On a failed apply the policy row keeps apply_error and the call answers 422. Only recording it would be a silent failure; only raising it would leave a stored policy nobody knows was never applied. ring is the staged-rollout ring this site belongs to — canary, early or general. It is a property of the site, not of the change, so an operator picks their canaries once and every later rollout inherits the choice. ⛔ Fleet only — refused where wp_update_policy is false, because it is written with wp config set and wp plugin auto-updates and this platform publishes no equivalent. Requires sites.view and sites.panel_access.

Parametreler

AdTürZorunluNe olduğu
siteId (path)UuidEvetSite ID (UUIDv7).

İstek gövdesi

AdTürZorunluNe olduğu
corestring<off, minor, all>Evetminor is WordPress's own default (security and maintenance releases); all includes major upgrades unattended; off disables core auto-updates.
pluginsbooleanEvetWhether every plugin should auto-update.
themesbooleanEvetWhether every theme should auto-update.
ringstring<canary, early, general>EvetThe staged-rollout ring this site belongs to.

Yanıt

AdTürZorunluNe olduğu
corestring<off, minor, all>EvetThe stored policy for WordPress core updates.
pluginsbooleanEvetThe stored policy — whether every plugin should auto-update.
themesbooleanEvetThe stored policy — whether every theme should auto-update.
ringstring<canary, early, general>EvetThe staged-rollout ring this site belongs to.
applied_atstringEvetWhen the policy last reached the site, ISO-8601, or "" if it never has. ⛔ A timestamp and not a flag: "when did this last reach the site" is the question an operator asks, and a…
apply_errorstringEvetWhy the last apply failed, or "". Kept beside applied_at rather than replacing it, so a failed re-apply does not erase that an earlier one worked.
observed_readbooleanEvetWhether the site itself was read. ⛔ An empty drift is only meaningful while this is true.
observed_corestringEvetWhat WP_AUTO_UPDATE_CORE is set to on the site — off, minor, all, or "" meaning the constant is not defined at all, so WordPress applies its own default. ⛔ "" is…
plugins_offstring[]EvetThe plugins on this site that are NOT auto-updating.
themes_offstring[]EvetThe themes on this site that are NOT auto-updating.
driftstring<core, plugins, themes>[]EvetWhich of core, plugins, themes the site disagrees with the policy about.

Bu uç noktanın dönderebileceği hatalar

401 · 403 · 404 · 422 · 429 · 503