hosting

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

Reinstall the live WordPress on a site.

所有 hosting 端点

身份验证

请将 API 密钥作为 bearer 令牌发送。该密钥必须具有 sites.view 权限;缺少该权限的密钥将被拒绝并返回 403 状态码,而非 404。

此端点不需要组织 ID。您的密钥已用于识别其所属的组织,且响应范围也仅限于该组织。

免费试用

将尖括号中的内容替换为您自己的值,并将键占位符替换为您仪表板中的一个键。

curl -X POST https://api.zinndigital.com/v1/sites/{siteId}/wordpress/reinstall \
  -H "Authorization: Bearer zdk_live_…"

已登录?您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥,并针对实时 API 运行请求,以便您查看实际的响应。 在 API 控制台中打开此端点

详细信息

⛔ **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`.

参数

名称类型必填内容简介
siteId (path)UuidSite ID (UUIDv7).

此端点可能返回的错误

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