API Update - September 15th, 2018 - The Bitfinex Blog
post-template-default,single,single-post,postid-17148,single-format-standard,bridge-core-3.0.6,et_bloom,qode-page-transition-enabled,ajax_fade,page_not_loaded,,qode-title-hidden,qode_grid_1300,footer_responsive_adv,qode-content-sidebar-responsive,qode-child-theme-ver-1.0.0,qode-theme-ver-29.3,qode-theme-bridge,qode_header_in_grid,wpb-js-composer js-comp-ver-6.10.0,vc_responsive

API Update – September 15th, 2018

Starting from September 15th, 2018, 00:00 UTC, Bitfinex will be implementing a series of changes to the way we manage WebSocket connections to our APIs.

As of September 15th, every WebSocket connection will have a limit of 250 subscriptions to 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. 

As an example, if you subscribe to all tickers, books, candles, trades channels on a single WebSocket connection, you’ll receive error:10305 (docs.bitfinex.com/v2/docs/ws-general#section-error-codes) to notify the quota if the current WebSocket connection is full.

For users, this means handling multiple streams, or running multiple instances and spreading them over different pairs. Implementing this API change results in improved connections for API users, meaning quicker data feeds and optimised trading strategies. Please note that you can still have a single feed for the authenticated feed. 

For a full overview of the Bitfinex API documentation, refer to the following page: docs.bitfinex.com/docs. For issues, please contact [email protected] with [API Update September 2018] as the email subject.



Stay up to date with Bitfinex on TwitterLinkedInTelegram, Facebook & YouTube

The Bitfinex APIs are designed to allow complete access to the features provided by Bitfinex. Learn more about our API documentation here.

We’ve recently open-sourced a number of the development libraries most essential to Bitfinex. If you are interested in learning more, visit our Github.