MetaDock WebSocket API
API by MetaDock · asyncapi
Real-time WebSocket API for MetaDock. Availability of individual actions and events depends on your MetaDock edition. One WebSocket endpoint at /ws carries every message. A client sends a JSON object whose type selects a handler and whose action selects the operation within it; arguments go in params. Where the same operation is also reachable over REST, its request body in openapi.yaml documents the same fields. Authentication The HTTP upgrade is not authenticated. The first message on a new connection must be {"type":"auth","api_key":"<uuid>"}; every other message is rejected until it succeeds. Five failed attempts close the socket, and the key must carry the websocket scope. A key scoped to specific profiles/layouts additionally has fleet-wide actions and out-of-scope browsers rejected. Responses and events Every request with an id is answered by a response carrying the same id. Events are pushed only for subscriptions the connection opened with a…
Verification: observed. Source: crawl.
Capabilities (23)
- receiveBrowserEvent
- receiveLayoutEvent
- receiveSystemEvent
- sendAdblock
- sendAuth
- sendBookmark
- sendBrowser
- sendDownload
- sendExtension
- sendHistory
- sendLayout
- sendNative_app
- sendPermission
- sendPing
- sendProfile
- sendProxy
- sendSearch
- sendSearch_engine
- sendSettings
- sendSubscribe
- sendTheme
- sendVideo
- sendWorkspace