hosting

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

Revoke a device.

Dhammaan hosting bixiyayaasha

Xaqiijinta aqoonsiga

U dir fure API ahaan calaamad muujisa (bearer token). Barta dhammaadka ee kani ma caysino luqad ahaan oggolaansho gaar ah oo ku dhex jirta qeexidda, markaa sii furahaaga inta ugu yar ee uu u baahan yahay oo fiiri jawaabta halka aad wax ka qaadan lahayd.

Boggan ma qaato aqoonsiga ururka. Furahaagu wuxuu horay u aqoonsanayaa ururka uu ka tirsan yahay, jawaabtuna waxay ku kooban tahay halkaas.

Isku day

Ku beddel wax kasta oo ku dhex jira qeebaha xaglaha ah qiimayaashaada, sidoo kalena haystaaha furaha ku beddel fure ka dhex muuqda dashboordigaaga.

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

Ma sign-garaysay? Qalabka API ee ku jira dashboard-kaagu wuxuu buuxiyaa aqoonsigaaga ururka ee dhabta ah iyo furahaaga gaarka ah, wuxuuna ku shaqeysiiyaa codsiga API-ga nool si aad u aragto jawaabta dhabta ah. Kani ka fur barta kontoroolka ee API

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.

Cabiraha

MagacaNoocLoo baahan yahayMaxay tahay
seatId (path)stringHaa

Jawaab

MagacaNoocLoo baahan yahayMaxay tahay
idstringHaa
labelstringHaaWhat the customer calls it — "Neil's MacBook".
addressstringHaaThe device's address inside the tunnel.
statusstring<active, revoked>Haa
created_atstringHaa
revoked_atstringMaya
last_seen_atstringMayaLast 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.

Cilladaha ay bartaani soo celin karto

401 · 403 · 404