hosting

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

Revoke a device.

Authentication

Send an API key as a bearer token. The key must carry the network.private.manage permission; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

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

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

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.

Parameters

Name	Type	Required	What it is
`seatId (path)`	`string`	Yes	—

Response

Name	Type	Required	What it is
`id`	`string`	Yes	—
`label`	`string`	Yes	What the customer calls it — "Neil's MacBook".
`address`	`string`	Yes	The device's address inside the tunnel.
`status`	`string<active, revoked>`	Yes	—
`created_at`	`string`	Yes	—
`revoked_at`	`string`	No	—
`last_seen_at`	`string`	No	Last 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.

Errors this endpoint can return

401 · 403 · 404

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