POST /v1/sites/{siteId}/wordpress/reinstall

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/reinstall \
  -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

⛔ Destructive. Replaces WordPress itself on the live site. It has its own path and takes no body, so it cannot be reached by flipping a field on reinstallSiteWordPressStaging — the platform separates the two with one nullable string, and one careless passthrough would make the live site reachable from a request that looks like a staging refresh. The vendor's acknowledgement is checked separately from its result: this endpoint answers a success object rather than the result field every other vendor call uses, and an absent result is not a refusal — reading it as one would report a refused reinstall of a customer's live WordPress as completed. 202 and no body. 404 for a site with no vendor hosting package. Requires sites.view and sites.panel_access.

Parameters

Errors this endpoint can return

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