hosting

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

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

Bütün hosting nöqtələri

Bütün tərtibatçı sənədləri

Doğrulama

API açarını bearer token kimi göndərin. Açar sites.view icazəsinə malik olmalıdır; bu icazəsi olmayan açar 404 deyil, 403 xətası ilə rədd edilir.

Bu endpoint heç bir təşkilat ID-si tələb etmir. Sizin açarınız artıq aid olduğu təşkilatı müəyyən edir və cavab həmin təşkilat üçün məhdudlaşdırılır.

Sınaqdan keçir

Bucaqlı mötərizələrdə olan hór şeyi öz qiymətlərinizlə, açar yertutucusunu isə idarə panelinizdən bir açarla əvəz edin.

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>> }'

Sistemə daxil olmusunuz? İdarə panelinizdəki API konsolu real təşkilatınızın identifikatorunu və öz açarınızı avtomatik doldurur, sorğunu canlı API-yə qarşı icra edir ki, siz faktiki cavabı görə biləsiniz. Bu son nöqtəni API konsolunda açın

Təfərrüatlar

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.

Parametrlər

AdTipTələb olunurNədir
siteId (path)UuidBəliSite ID (UUIDv7).

Sorğu gövdəsi

AdTipTələb olunurNədir
corestring<off, minor, all>Bəliminor is WordPress's own default (security and maintenance releases); all includes major upgrades unattended; off disables core auto-updates.
pluginsbooleanBəliWhether every plugin should auto-update.
themesbooleanBəliWhether every theme should auto-update.
ringstring<canary, early, general>BəliThe staged-rollout ring this site belongs to.

Cavab

AdTipTələb olunurNədir
corestring<off, minor, all>BəliThe stored policy for WordPress core updates.
pluginsbooleanBəliThe stored policy — whether every plugin should auto-update.
themesbooleanBəliThe stored policy — whether every theme should auto-update.
ringstring<canary, early, general>BəliThe staged-rollout ring this site belongs to.
applied_atstringBəliWhen 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_errorstringBəliWhy 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_readbooleanBəliWhether the site itself was read. ⛔ An empty drift is only meaningful while this is true.
observed_corestringBəliWhat 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[]BəliThe plugins on this site that are NOT auto-updating.
themes_offstring[]BəliThe themes on this site that are NOT auto-updating.
driftstring<core, plugins, themes>[]BəliWhich of core, plugins, themes the site disagrees with the policy about.

Bu son nöqtənin qaytara biləcəyi xətalar

401 · 403 · 404 · 422 · 429 · 503