DELETE /v1/compute/servers/{serverId}/add-on

身份验证

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

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

免费试用

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

curl -X DELETE https://api.zinndigital.com/v1/compute/servers/{serverId}/add-on \
  -H "Authorization: Bearer zdk_live_…"

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

详细信息

Stops the charge and gives the licence back to the vendor. Requires `sites.view` and `billing.payment.manage`, the same pair as buying one. ⛔ Not `sites.delete`: cancelling destroys no customer data, it stops a cost — and putting it behind the wipe key would stop a customer turning off something they are paying for. ⛔⛔ And not `billing.entitlement.manage`, which is what it was until 2026-08-17: no customer role holds that key, so the customer paying $29 a month for the managed service was the one person who could not stop paying it. The machine's recurring price falls by the add-on's amount **from the next period**. The period already paid for is honoured rather than clawed back. ⛔ **The vendor is released before our row is marked**, deliberately. If the vendor call fails we keep an active row and go on paying, which is visible and swept for; the other order loses the licence from our side while the vendor keeps billing it — an orphan no sweep can find, because the row naming the address is gone. ⭐ For a pooled licence (LiteSpeed) the seat goes to `releasing`, not `free`: the serial is IP-bound and the release is manual in the vendor's own portal, so returning it to stock would hand the next customer a serial still locked to somebody else.

参数

响应

此端点可能返回的错误

401 · 403 · 404 · 422 · 429