Web Socket Subscriptions
Subscriptions requests are sent through a web socket connection. To subscribe to a feed, a web socket connection is required to establish a connection using the following URL:
Keeping the connection alive
In order to keep the websocket connection alive, you will need to make a ping request at least every 60 seconds. You can see this in our sample implementation.
Snapshots and Updates
For ease of use, most web socket feeds first send a snapshot of the history or current state and
subsequently send real-time updates.
In order to subscription to a private feed, users musts pass a challenge which involves signing a message (see Section Sign Challenge) with the private API key. First, a message must be sent to request the challenge. Second, the solved challenge has to be passed in every subscribe and unsubscribe message that is sent.