hosting

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

Revoke a device.

Dukkan hosting wuraren ƙarshe

Tabbatar da Asali

Aiko da maɓallin API a matsayin bearer token. Wannan ma'anar ba ta bayyana takamaiman izini ba a cikin ƙayyadaddun bayanai, don haka ba wa maɓallin ku mafi ƙarancin abin da yake buƙata kuma ku bincika amsar maimakon yin zato.

Wannan wurin ƙarewa ba ya buƙatar ID na ƙungiya. Maɓallin ku ya riga ya gano ƙungiyar da yake ciki, kuma an iyakance amsa a kanta.

Gwada

May gurbin komai da ke cikin kusurwa da ƙimar ka, kuma may gurbin maballi da maballi daga allon sarrafa ka.

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

An shiga? Na'urar sarrafa API da ke cikin sashin kulawarka tana cika ainihin lambar ƙungiyarka da maɓallinka naka, sannan tana gudanar da buƙatar a kan ainihin API don haka zaka iya ganin amsar gaske. Buɗe wannan tashar a cikin na'urar kula da API

Bayani

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.

Sigogi

SunaNau'iAna buƙataAbin da yake
seatId (path)stringEh

Martani

SunaNau'iAna buƙataAbin da yake
idstringEh
labelstringEhWhat the customer calls it — "Neil's MacBook".
addressstringEhThe device's address inside the tunnel.
statusstring<active, revoked>Eh
created_atstringEh
revoked_atstringA'a
last_seen_atstringA'aLast 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.

Kuskuren da wannan matsaya za ta iya maido wa

401 · 403 · 404