hosting

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

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

Svi hosting krajnji točke

Sva developerska dokumentacija

Autentifikacija

Pošaljite API ključ kao nosivi token. Ključ mora imati dozvolu sites.view; ključ bez nje se odbija s kodom 403, a ne 404.

Ova krajnja točka ne prihvaća ID organizacije. Vaš ključ već identificira organizaciju kojoj pripada, a odgovor je ograničen na nju.

Isprobajte

Zamijenite sve unutar šiljastih zagrada svojim vlastitim vrijednostima, a rezervirano mjesto za ključ s ključem iz vaše nadzorne ploče.

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

Prijavljeni ste? API konzola na vašoj nadzornoj ploči automatski unosi stvarni ID vaše organizacije i vaš vlastiti ključ te šalje zahtjev prema aktivnom API-ju kako biste mogli vidjeti stvarni odgovor. Otvori ovu krajnju točku u API konzoli

Pojedinosti

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.

Parametri

NazivVrstaObaveznoŠto je to
siteId (path)UuidDaSite ID (UUIDv7).

Tijelo zahtjeva

NazivVrstaObaveznoŠto je to
corestring<off, minor, all>Daminor is WordPress's own default (security and maintenance releases); all includes major upgrades unattended; off disables core auto-updates.
pluginsbooleanDaWhether every plugin should auto-update.
themesbooleanDaWhether every theme should auto-update.
ringstring<canary, early, general>DaThe staged-rollout ring this site belongs to.

Odgovor

NazivVrstaObaveznoŠto je to
corestring<off, minor, all>DaThe stored policy for WordPress core updates.
pluginsbooleanDaThe stored policy — whether every plugin should auto-update.
themesbooleanDaThe stored policy — whether every theme should auto-update.
ringstring<canary, early, general>DaThe staged-rollout ring this site belongs to.
applied_atstringDaWhen 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_errorstringDaWhy 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_readbooleanDaWhether the site itself was read. ⛔ An empty drift is only meaningful while this is true.
observed_corestringDaWhat 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[]DaThe plugins on this site that are NOT auto-updating.
themes_offstring[]DaThe themes on this site that are NOT auto-updating.
driftstring<core, plugins, themes>[]DaWhich of core, plugins, themes the site disagrees with the policy about.

Pogreške koje ova krajnja točka može vratiti

401 · 403 · 404 · 422 · 429 · 503