hosting
POST /v1/sites/{siteId}/wordpress/stack-cache
Install the server-side cache plugin on a site.
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/stack-cache \
-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
Installs the platform's own caching plugin. It has its own operation rather than being a row in the plugin listing because the vendor **excludes it from that listing**, so it can neither be found there nor installed through it. Success is confirmed by the vendor's own `stackCacheInstalled` flag, never by searching the returned rows for it — searching a list the plugin is deliberately absent from would report failure on every successful install. `201` and the whole plugin listing, so the card re-renders. `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). |
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 · 409 · 422 · 429 · 503