Real-time streaming protocols (WebSocket and FIX) are restricted by the data types available and the maximum number of connections/sessions that can be established concurrently. More information about the specific limits on each plan you can find on our Pricing page  and API Documentation .
What are the risks of having multiple concurrent connections for Websocket?
Currently, subscriptions have a soft limit of a single concurrent connection for Websocket. If you are using multiple concurrent connections, the risk is in the fact that the credentials are shared between environments, and this could lead to misuse of the key or leakage affecting the production environment. If the key is misused, it could trigger some of the hard limits regarding concurrency that could affect the production.
Please sign in to leave a comment.