hosting
POST /v1/sites/{siteId}/wordpress/plugins/{pluginName}/update
Update one plugin to its latest release.
Authentication
Send an API key as a bearer token. The key must carry the sites.view permission; a key without it is refused with 403, not 404.
This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.
Try it
Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.
curl -X POST https://api.zinndigital.com/v1/sites/{siteId}/wordpress/plugins/{pluginName}/update \
-H "Authorization: Bearer zdk_live_…"Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console
Details
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`.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
siteId (path) | Uuid | Yes | Site ID (UUIDv7). |
pluginName (path) | string | Yes | The plugin's slug, exactly as `listSiteWordPressPlugins` reports it. |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
data | SiteWordPressPlugin[] | Yes | The installed plugins. |
stack_cache_installed | boolean | Yes | ⛔ **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… |
Errors this endpoint can return
401 · 403 · 404 · 422 · 429 · 503