Skip to main content
Use Coda WebSocket v1 for new Coda integrations. For Mist, select an endpoint from the support table below.

Choose a model and protocol

Mist v1 and Mist v2 also support /ws3. For all Mist JSON and raw-audio options, see the Mist endpoint support table.

Authenticate from your server

Your server sends Authorization: Bearer YOUR_API_KEY during the WebSocket upgrade. Create a key on the API Tokens page. Keep credentials on the server. A browser’s WebSocket object cannot set this header, so browser applications need a backend bridge that connects to Rime. See API authentication.

Choose a Coda client

Both encodings support streaming text, persistent connections, context IDs, and cancellation. Neither supplies word timestamps. Binary avoids base64 encoding. Decode its Protobuf envelope before playing audio. Use the Coda WebSocket API reference for parameters, lifecycle, and errors.

Mist endpoint support

Mist uses wss://users-ws.rime.ai with the paths below. Use /ws3 for new Mist integrations. Existing Mist v1 and Mist v2 clients can continue to use /ws2. The Mist v3 JSON reference documents /ws3. The Mist v2 JSON reference documents /ws2; Mist v2 also supports /ws3 with the same JSON message format. /ws2 does not receive new model support. For raw audio, see the Mist v3 raw WebSocket reference or Mist v2 raw WebSocket reference. The /ws endpoint returns audio bytes without JSON framing, word timestamps, context IDs, or structured error events. For text buffering and the flush, clear, and eos operations on the Mist JSON endpoints, see the segmentation guide.