hosting

DELETE /v1/private-network/devices/{seatId}

Revoke a device.

所有 hosting 端点

身份验证

请将 API 密钥作为 bearer 令牌发送。此端点在规范中未指明具体的权限,因此请为您的密钥赋予所需的最小权限,并通过检查响应来确认,而不是盲目假设。

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

免费试用

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

curl -X DELETE https://api.zinndigital.com/v1/private-network/devices/{seatId} \
  -H "Authorization: Bearer zdk_live_…"

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

详细信息

Gated on `network.private.manage`. The row is kept, marked revoked, so the revocation can be evidenced later — a revocation nobody can point at is not much of a control. ⚠️ Access stops when the gateway next syncs its peer set, not at the instant this returns. The dashboard says so rather than implying otherwise. 404 rather than 403 for a device in another tenant — a 403 would confirm it exists.

参数

名称类型必填内容简介
seatId (path)string

响应

名称类型必填内容简介
idstring
labelstringWhat the customer calls it — "Neil's MacBook".
addressstringThe device's address inside the tunnel.
statusstring<active, revoked>
created_atstring
revoked_atstring
last_seen_atstringLast handshake the gateway reported. Null until the device first connects, which is what makes "you are paying for five devices and three have never been used" answerable.

此端点可能返回的错误

401 · 403 · 404