hosting
DELETE /v1/sites/{siteId}/wordpress/plugins/{pluginName}
Remove a plugin from a site's WordPress.
身份验证
请将 API 密钥作为 bearer 令牌发送。该密钥必须具有 sites.view 权限；缺少该权限的密钥将被拒绝并返回 403 状态码，而非 404。
此端点不需要组织 ID。您的密钥已用于识别其所属的组织，且响应范围也仅限于该组织。
免费试用
将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。
curl -X DELETE https://api.zinndigital.com/v1/sites/{siteId}/wordpress/plugins/{pluginName} \
-H "Authorization: Bearer zdk_live_…"已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
Deletes the plugin's files. **Whatever it stored in the database stays**, and whatever it was doing for the site stops — so the client confirms the name back before calling. ⛔ The listing is re-read afterwards and a plugin that survived the removal is reported as a refusal rather than a success: the platform acknowledges a delete it did not perform, and a card that removed the row locally would show the customer a plugin that is still running. `200` and the whole listing, not `204`, because the card renders the remaining plugins from this answer. `404` for a site with no vendor hosting package. Requires `sites.view` and `sites.panel_access`.
参数
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
siteId (path) | Uuid | 是 | Site ID (UUIDv7). |
pluginName (path) | string | 是 | The plugin's slug, exactly as `listSiteWordPressPlugins` reports it. It is WordPress's identifier, not ours, so percent-encode it; a slug containing a slash does not route and a… |
响应
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
data | SiteWordPressPlugin[] | 是 | The installed plugins. |
stack_cache_installed | boolean | 是 | ⛔ **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… |
此端点可能返回的错误
401 · 403 · 404 · 409 · 422 · 429 · 503