hosting

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

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

Pagpapatotoo

Magpadala ng API key bilang isang bearer token. Kailangang taglayin ng key ang pahintulot na sites.view; ang key na wala nito ay tatanggihan gamit ang 403, hindi 404.

Ang endpoint na ito ay hindi nangangailangan ng id ng organisasyon. Natutukoy na ng iyong key ang organisasyong kinabibilangan nito, at nakatuon ang tugon dito.

Subukan ito

Palitan ang anuman sa loob ng mga panaklong na may anggulo ng iyong sariling mga halaga, at ang placeholder ng key na may key mula sa iyong dashboard.

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

Nakalagda? Ang API console sa iyong dashboard ay awtomatikong naglalagay ng iyong tunay na ID ng organisasyon at sariling susi, at pinapatakbo ang kahilingan laban sa live na API upang makita mo ang aktwal na tugon. Buksan ang endpoint na ito sa console ng API

Mga Detalye

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`.

Mga Parameter

Pangalan	Uri	Kailangan	Ano ito
`siteId (path)`	`Uuid`	Oo	Site ID (UUIDv7).

Katawan ng kahilingan

Pangalan	Uri	Kailangan	Ano ito
`core`	`string<off, minor, all>`	Oo	`minor` is WordPress's own default (security and maintenance releases); `all` includes major upgrades unattended; `off` disables core auto-updates.
`plugins`	`boolean`	Oo	Whether every plugin should auto-update.
`themes`	`boolean`	Oo	Whether every theme should auto-update.
`ring`	`string<canary, early, general>`	Oo	The staged-rollout ring this site belongs to.

Tugon

Pangalan	Uri	Kailangan	Ano ito
`core`	`string<off, minor, all>`	Oo	The stored policy for WordPress core updates.
`plugins`	`boolean`	Oo	The stored policy — whether every plugin should auto-update.
`themes`	`boolean`	Oo	The stored policy — whether every theme should auto-update.
`ring`	`string<canary, early, general>`	Oo	The staged-rollout ring this site belongs to.
`applied_at`	`string`	Oo	When 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…
`apply_error`	`string`	Oo	Why 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_read`	`boolean`	Oo	Whether the site itself was read. ⛔ An empty `drift` is only meaningful while this is `true`.
`observed_core`	`string`	Oo	What `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_off`	`string[]`	Oo	The plugins on this site that are NOT auto-updating.
`themes_off`	`string[]`	Oo	The themes on this site that are NOT auto-updating.
`drift`	`string<core, plugins, themes>[]`	Oo	Which of `core`, `plugins`, `themes` the site disagrees with the policy about.

Mga error na maibabalik ng endpoint na ito

401 · 403 · 404 · 422 · 429 · 503

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