# Limits & quotas URL: /stt/rt/limits-and-quotas Learn about real-time API limits and quotas. ## WebSocket API limits Soniox applies limits to real-time WebSocket sessions to ensure stability and fair use. Make sure your application respects these constraints and implements graceful recovery when a limit is reached. | Limit | Value | Notes | | ---------------------- | ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Requests per minute | **100** | Exceeding this may result in rate limiting | | Concurrent requests | **10** | Maximum number of simultaneous active streams | | Concurrent connections | **Multiple of concurrent requests** | Maximum number of open WebSocket connections, including idle ones. Derived from the concurrent requests limit; not set separately. Exceeding it returns [`max_concurrent_connections_reached`](/api-reference/errors#max-concurrent-connections-reached). See [WebSocket authentication](/guides/websocket-authentication#connection-limit). | | Stream duration | **300 minutes** | Each real-time session is capped at 300 minutes. To continue beyond this, open a new session.
**This limit is fixed and cannot be increased** | You can request higher limits (except for stream duration) in the [Soniox Console](https://console.soniox.com/). The concurrent connections limit follows the concurrent requests limit. Learn how to [track usage](/guides/usage-logs) and [monitor concurrency](/guides/concurrency-limits).