Upcoming Bitfinex API Update — June 2019
An overview of upcoming changes to the Bitfinex API
Starting from June 22nd, 08:00 UTC, Bitfinex will be implementing a change to the way we manage WebSocket connections to our APIs.
As of June 22nd, every WebSocket connection will have a limit of 30 subscriptions to public market data feed channels (tickers, book, candles, trades, …). We kindly ask all users to adapt their application setup accordingly to split subscriptions to channels using multiple WebSocket connections.
For all affected users, this update means handling multiple streams (or running multiple instances and spreading them over different pairs). Please note that this change does not affect the authenticated feed.
Moving forwards, all users who do not reconfigure their API settings will be met with an error message. As an example, if you exceed the allowed subscription quota for channels on a single WebSocket connection, you will receive error:10305 to notify the quota that the current WebSocket connection is full.
Benefits of Update
Implementing this change will result in an improved connection for API users, resulting in quicker data feeds and enhanced trade execution. The reasoning behind this change is to allow our systems to scale better, thus allowing us to provide improved load management. Users that subscribe to too many public market channels (i.e. above 250) on a single connection are ultimately experiencing a degraded latency due to the quantity of data sent, and this API update will help mitigate said load.
All our API libraries (NodeJS, Ruby, Go) are updated with the new logic (30 channels per connection).
For a full overview of the Bitfinex API documentation, refer to the following page: docs.bitfinex.com/docs. For any issues or concerns, please refer to bitfinex.com/support for assistance.
