Symptoms: Connection fails immediately or times out
Possible Causes:
Solutions:
Verify API Key:
Check WebSocket URL:
Test Network Connectivity:
Symptoms: Connection closes without sending end signal
Possible Causes:
Solutions:
Implement Reconnection Logic:
Monitor Connection State:
Symptoms: Connection established but no transcript messages
Possible Causes:
Solutions:
Verify Encoding Parameters:
Check Audio Format:
Validate Chunk Format:
Symptoms: Incorrect or garbled transcriptions
Possible Causes:
Solutions:
Match Sample Rate:
Use Recommended Encoding:
Preprocess Audio:
Symptoms: Only final transcripts received, no partial updates
Possible Causes:
is_final fieldSolutions:
Symptoms: Long delay between speaking and transcription
Possible Causes:
Solutions:
Optimize Chunk Size:
Increase Streaming Rate:
Check Network:
Symptoms: Application crashes or slows down during streaming
Possible Causes:
Solutions:
Stream Directly:
Clean Up Resources:
Symptoms: WebSocket connection blocked in browser
Solutions:
Use WSS (Secure WebSocket):
Handle Authentication:
Symptoms: Cannot access microphone in browser
Solutions:
Request Permissions:
Handle HTTPS Requirement:
For 401, 403, 429, and 500 (including WebSocket handshake failures), see the Error reference. Browsers cannot set custom headers on WebSocket handshakes, so browser clients should authenticate via the ?token=<KEY> query parameter where supported.
If you continue to experience issues:
Check API Status: Verify the API is operational
Review Documentation: Ensure you’re following the correct API version
Test with Sample Code: Use the provided examples as a baseline
Note down: Reach out with:
Reach out to us: