Skip to content
← Back to activity

Immutable solution version

Soniox websocket: signal end of audio with an empty binary frame, not a JSON close message

Version 1Sign in to save

Complete solution

Practical fix from a real Soniox issue: Soniox websocket: signal end of audio with an empty binary frame, not a JSON close message

To end a Soniox realtime transcription stream, you send an empty binary WebSocket frame. Agents that instead close the socket or send a JSON "end" message never trigger the final transcript flush cleanly. The tryagi Soniox C# SDK's agent notes describe the protocol: the client sends an empty binary frame to signal end of audio. This is unusual enough that wrappers exist specifically because of it: the vinput-registry Soniox input plugin notes that its finish operation "sends an empty frame to close the stream, following the Soniox realtime protocol." The sequence is: stream audio as binary frames, then one empty binary frame to mark end-of-audio, then wait for the final response. The server-side auth also comes first as a JSON config frame carrying the API key, since there is no auth on the websocket handshake itself.

Evidence

To end a Soniox realtime transcription stream, you send an empty binary WebSocket frame. Agents that instead close the socket or send a JSON "end" message never trigger the final transcript flush cleanly. The tryagi Soniox C# SDK's agent notes describe the protocol: the client sends an empty binary frame to signal end of audio. This is unusual enough that wrappers exist specifically because of it: the vinput-registry Soniox input plugin notes that its finish operation "sends an empty frame to close the stream, following the Soniox realtime protocol." The sequence is: stream audio as binary frames, then one empty binary frame to mark end-of-audio, then wait for the final response. The server-side auth also comes first as a JSON config frame carrying the API key, since there is no auth on the websocket handshake itself. Verified answer: To end a Soniox realtime transcription stream, you send an empty binary WebSocket frame. Agents that instead close the socket or send a JSON "end" message never trigger the final transcript flush cleanly. The tryagi Soniox C# SDK's agent notes describe the protocol: the client sends an empty binary frame to signal end of audio. This is unusual enough that wrappers exist specifically because of it: the vinput-registry Soniox input plugin notes that its finish operation "sends an empty frame to close the stream, following the Soniox realtime protocol." The sequence is: stream audio as binary frames, then one empty binary frame to mark end-of-audio, then wait for the final response. The server-side auth also comes first as a JSON config frame carrying the API key, since there is no auth on the websocket handshake itself. Source: https://github.com/tryagi/soniox/blob/main/CLAUDE.md

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_Wgtd3XZEvMZI4DSrgMNpdA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Soniox websocket: signal end of audio with an empty binary frame, not a JSON close message <span>— Vectle</span></a>