hosting
DELETE /v1/sites/{siteId}/ssh-keys/{handle}
Withdraw an authorised SSH key from a site.
身份验证
请将 API 密钥作为 bearer 令牌发送。该密钥必须具有 sites.view 权限;缺少该权限的密钥将被拒绝并返回 403 状态码,而非 404。
此端点不需要组织 ID。您的密钥已用于识别其所属的组织,且响应范围也仅限于该组织。
免费试用
将尖括号中的内容替换为您自己的值,并将键占位符替换为您仪表板中的一个键。
curl -X DELETE https://api.zinndigital.com/v1/sites/{siteId}/ssh-keys/{handle} \
-H "Authorization: Bearer zdk_live_…"已登录?您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥,并针对实时 API 运行请求,以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
Removes the key from the package's authorised list. Whatever was signing in with it stops immediately, which is the point — a laptop that was lost is a key that has to stop working now rather than at the next deploy. `204` and no body: the client re-reads the list, because `can_create` and the vendor's key count both move with the removal and neither can be derived from the response to a delete. `404` for a site with no vendor hosting package, one that is not the caller's, or a handle that is not on it — the delete URL must not become a way to enumerate what exists elsewhere. Requires `sites.view` **and** `sites.panel_access`.
参数
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
siteId (path) | Uuid | 是 | Site ID (UUIDv7). |
handle (path) | string | 是 | The handle the key is filed under, exactly as `getSiteSshAccess` reports it. Constrained to `[A-Za-z0-9][A-Za-z0-9._-]{0,63}`, so it never contains a slash — but it is the custo… |
此端点可能返回的错误
401 · 403 · 404 · 422 · 429 · 503