hosting

POST /v1/sites/{siteId}/wordpress/plugins/{pluginName}/update

Update one plugin to its latest release.

所有 hosting 端点

身份验证

请将 API 密钥作为 bearer 令牌发送。该密钥必须具有 sites.view 权限;缺少该权限的密钥将被拒绝并返回 403 状态码,而非 404。

此端点不需要组织 ID。您的密钥已用于识别其所属的组织,且响应范围也仅限于该组织。

免费试用

将尖括号中的内容替换为您自己的值,并将键占位符替换为您仪表板中的一个键。

curl -X POST https://api.zinndigital.com/v1/sites/{siteId}/wordpress/plugins/{pluginName}/update \
  -H "Authorization: Bearer zdk_live_…"

已登录?您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥,并针对实时 API 运行请求,以便您查看实际的响应。 在 API 控制台中打开此端点

详细信息

Updates a single plugin and returns the whole plugin list. The listing is re-read rather than patched: an update can deactivate a plugin whose new version declares a requirement the site does not meet, and a client shown an optimistic guess would render it as active. Idempotent, and its own path segment, for the same reasons as the theme twin above. ⛔ **Fleet only** — refused where `wp_component_updates` is `false`. Requires `sites.view` and `sites.panel_access`.

参数

名称类型必填内容简介
siteId (path)UuidSite ID (UUIDv7).
pluginName (path)stringThe plugin's slug, exactly as `listSiteWordPressPlugins` reports it.

响应

名称类型必填内容简介
dataSiteWordPressPlugin[]The installed plugins.
stack_cache_installedboolean⛔ **Cannot be derived from `data`.** this platform excludes its own server-side cache plugin from the listing, so a client deriving this flag from the rows would answer "not ins…

此端点可能返回的错误

401 · 403 · 404 · 422 · 429 · 503