POST /v1/sites/{siteId}/wordpress/themes/{themeName}/update

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/themes/{themeName}/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 theme and returns the whole theme list. ⛔ **Its own path segment, not a field on the `PUT` beside activate/deactivate.** Updating replaces the theme's files on a live site; activating changes which one renders. A caller that got a body wrong must not be able to reach the first by aiming at the second — the rule every destructive operation on this surface follows. Idempotent: a theme already on its latest version is a successful no-op, so a caller may run this across a selection without first filtering to the ones that need it. ⛔ **Fleet only** — this platform has no per-component update verb at any path (only `updateSiteWordPressCore`, which moves WordPress itself). Refused where `wp_component_updates` is `false`. Requires `sites.view` and `sites.panel_access`.

Parameters

Response

Errors this endpoint can return

401 · 403 · 404 · 422 · 429 · 503