Limits

We have one common limit for no more than 1000 market subscriptions within one websocket connection.

Connections

If the user runs out of allowed connections, they will not be able to establish a new one. They will get the 429 Too Many Requests HTTP error code with a message in the header like: The number of websocket sessions has exceeded. Limit: ${tier.maxConnections}.

Traffic

We measure the client’s traffic for the last 24h window every minute. You can find the amount of transferred data in the HTTP response header x-inca-websocket-transferred-bytes when opening a websocket connection.

If the traffic limit is exceeded, we close all of the user’s websocket connections. Any attempt to open a new websocket connection will result in a 429 Too Many Requests HTTP error code with a message in the header like: The number of transferBytes has exceeded. Limit: ${tier.maxTransferBytes}.

Before dropping a user’s websocket sessions, the following message will be sent:

{
  "type":"error-too-many-requests",
  "payload": {
    "message": "The number of transferBytes has exceeded. Limit: ${tier.maxTransferBytes}."
  }
}