Skip to main contentSee rate limit applied to opening new WebSocket connections. Total Concurrent Connection Limit
WebSocket connections are subject to concurrent connection limits that vary by user type and connection scope. These limits are shared between UI and API access and can be increased upon request.
Market Makers
Market-Specific Connections:
| WebSocket Type | Connections per Market |
|---|
| Order Creation | 4 |
| All Other WebSockets | 2 |
Market-Agnostic Connections:
The limit is calculated as: Per-market limit × Number of supported markets
Retail/Institutional Users
| Connection Type | Limit |
|---|
| Market-Specific | 5 |
| Market-Agnostic | 5 |
If you exceed the concurrent connection limit, you will receive a 403 Forbidden response when attempting to establish additional connections.
Best Practices
We should always close the old connection explicitly before opening a new one. This will not only help you avoid hitting the total concurrent connection limit, but also ensure that
you get the best performance from the WebSocket API. If you need to check your orders from our exchange UI, make sure that you only have one browser tab open because
the connections from the UI count towards the limit as well. 
