PulseLab

WebSockets

Connecting

Save a WebSocket connection once and connect to it with a single click.

Creating a connection

From the dashboard, click "New connection" and fill in:

  • Name — anything memorable.
  • URL — must start with ws:// or wss://.
  • Subprotocols (optional).
  • Headers (optional) — JSON object.

URL examples

Some valid URLs you can save:

urls
wss://echo.example.com
wss://your-app.com/socket
ws://localhost:8080
  • wss://echo.example.com — Public echo server for testing.
  • wss://your-app.com/socket — Your own production WebSocket endpoint.
  • ws://localhost:8080 — Local development server.

Subprotocols

Some servers expect a specific subprotocol negotiated during the handshake:

  • graphql-ws — GraphQL over WebSockets (Apollo, urql).
  • mqtt — MQTT messaging.
  • json — Often a hint, not a real subprotocol.

Headers

Browsers don't allow custom WebSocket headers. We store them anyway — useful when exporting to other clients.

Connection status

  • Connecting — Browser is opening the socket.
  • Connected — The socket is open and ready.
  • Disconnected — The socket is closed.
  • Error — Something went wrong.

Plan limits

Free: up to 3 saved connections. Pro: unlimited.