Skip to main content
Connect a relay bridge (WebSocket)
There is no Try-it control on this page, on purpose. This address is a WebSocket upgrade, not a request/response GET, so it cannot be exercised over HTTP — the playground is suppressed rather than offered and left to fail. Dial it with wss:// from a WebSocket client, or run the enkryptai-relay console script that ships in the Python SDK, which does all of this for you.For the end-to-end walkthrough — running the bridge, confirming it is connected, and pointing a run at it — see Red Teaming Through the Relay Bridge.

Authorizations

apikey
string
header
required

Headers

Upgrade
string
required

Must be websocket. Sent for you by any WebSocket client library.

Example:

"websocket"

x-enkrypt-relay-bridge-id
string
required

The identifier this bridge registers under. Free text you choose, and the one value both sides must agree on: it has to equal target.metadata.relay.bridge_id on the runs you want routed here, and it is what RELAY_BRIDGE_ID sets on the SDK bridge. Scoped to your account, so it only has to be unique within it.

Example:

"customer-bridge-1"

Response

Switching Protocols - the bridge is registered and will now receive relayed requests on this socket.