WebSocket requests

Create one with New → WebSocket Request, or Add WebSocket request on a collection or folder. It's saved like any request (shown as WS), so it lives in collections and syncs with your team.

• Connect to a ws:// or wss:// URL. {{variables}} work in the URL, headers and messages.
• Handshake: your headers, plus the auth inherited from the collection or folder (Bearer, Basic, API key, OAuth 2.0…) and matching cookies, are sent with the handshake. Subprotocols go in Settings. Client certificates, trusted CAs, the proxy and SSL verification apply as for HTTP. Click the "Connected" line in the log to see the exact handshake.
• Messages: write text or JSON and press Send (or Ctrl/Cmd+Enter, which connects first if the tab isn't connected). Save messages you use often and reuse them with one click.
• Log: everything sent (↑) and received (↓) with times and sizes. Click a message to see it pretty-printed and copy it; filter as you type. Pings are answered automatically, and the close code and reason are shown when the connection ends.
• If the server refuses the upgrade, its status and response body are shown, so a 401 or 403 is easy to diagnose.

The collection runner, mock servers and Postman export skip WebSocket requests.