connect.device.manage

Generated at from openvibe-contracts v0.419.0 and openvibe-sdk v0.161.0.

Not grantable to apps (planned, public).

PLANNED for OpenVibe.Website Connect (audience openvibe.website, owner or project scope): approve a pending device, change its name, tags, routes or exit-node setting, or remove it (POST /api/v1/devices/:id/approve, PATCH /api/v1/devices/:id, DELETE /api/v1/devices/:id) as connect.device@1. Removal revokes the mesh key at the control plane at once; an approval never admits a device to another tenant. Pre-auth keys and WireGuard keys are never returned or logged.

Owner
connect (token audience openvibe.connect)
Version
1.0
Status
planned
Visibility
public
Resource constraints
owner, project
Quota class
connect-device
Permissions
connect:devices:manage
Input
connect.device@1
Output
connect.device@1
Events
—
Implemented by
  • POST /api/v1/devices/:id/approve
  • PATCH /api/v1/devices/:id
  • DELETE /api/v1/devices/:id

These routes in the API explorer