hosting

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

Revoke a device.

Vituo vyote vya hosting

Uthibitishaji

Tuma ufunguo wa API kama tokeni ya kubeba. Sehemu hii ya mwisho haitaji ruhusa maalum katika maelezo, kwa hivyo ipe ufunguo wako kiwango cha chini kabisa kinachohitajika na uangalie jibu badala ya kukisia.

Endpoint hii haichukui kitambulisho cha shirika. Ufunguo wako tayari unalitambua shirika linalohusika, na jibu limewekewa kikomo kwa shirika hilo pekee.

Jaribu

Badilisha chochote kilicho ndani ya mabano ya pembe na maadili yako mwenyewe, na kishikiliaji cha ufunguo na ufunguo kutoka kwa dashibodi yako.

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

Umeingia kwenye akaunti? Dashibodi yako ya kiweko cha API inajaza kitambulisho chako halisi cha shirika na ufunguo wako mwenyewe, na kuendesha ombi dhidi ya API ya moja kwa moja ili uweze kuona jibu halisi. Fungua sehemu hii ya mwisho (endpoint) kwenye konsole ya API

Maelezo

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.

Vigezo

JinaAinaInayohitajikaKilicho hiki
seatId (path)stringNdiyo

Majibu

JinaAinaInayohitajikaKilicho hiki
idstringNdiyo
labelstringNdiyoWhat the customer calls it — "Neil's MacBook".
addressstringNdiyoThe device's address inside the tunnel.
statusstring<active, revoked>Ndiyo
created_atstringNdiyo
revoked_atstringHapana
last_seen_atstringHapanaLast 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.

Hitilafu ambazo mwisho huu unaweza kurudisha

401 · 403 · 404