Streaming
The Streaming Speech-to-Text service leverages WebSockets. This section details the endpoints and procedures necessary for utilizing the streaming functionality, including:
- POST endpoint to obtain a temporary token for authentication
- WebSockets API reference with detailed information on managing WebSocket connections for streaming
Below, you’ll also find information on error codes and limits.
Close and error codes
The WebSocket specification provides standard errors. Additionally, the API returns application-level errors for well-known scenarios:
Quotas and Limits
The following limits are imposed to ensure performance and service quality:
- Idle Sessions - Sessions that don’t receive audio within 1 minute will be terminated.
- Session Limit - 100 sessions at a time for paid users. Please contact us if you need to increase this limit. Free-tier users must upgrade their account to use real-time streaming.
- Session Uniqueness - Only one WebSocket per session.
- Audio Sampling Rate Limit - Customers must send data in near real-time. If a client sends data faster than 1 second of audio per second for longer than 1 minute, we’ll terminate the session.