hosting

DELETE `/v1/sites/{siteId}/wordpress/themes/{themeName}`

Remove a theme from a site's WordPress.

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 DELETE https://api.zinndigital.com/v1/sites/{siteId}/wordpress/themes/{themeName} \
  -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

Deletes the theme's files. The list is re-read afterwards, so a theme that survived the removal is a refusal rather than a reported success. `200` and the whole list, because the card renders the remainder from this answer. `404` for a site with no vendor hosting package. Requires `sites.view` and `sites.panel_access`.

Parameters

Name	Type	Required	What it is
`siteId (path)`	`Uuid`	Yes	Site ID (UUIDv7).
`themeName (path)`	`string`	Yes	The theme's slug, exactly as `listSiteWordPressThemes` reports it. WordPress's identifier, not ours — percent-encode it.

Response

Name	Type	Required	What it is
`data`	`SiteWordPressTheme[]`	Yes	The installed themes.

Errors this endpoint can return

401 · 403 · 404 · 409 · 422 · 429 · 503

DELETE /v1/sites/{siteId}/wordpress/themes/{themeName}