API Update – September 1st, 2018

API Update – September 1st, 2018

Starting from September 1st, 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 1st, every WebSocket connection will have a limit of 50 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.

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

Stay up to date with Bitfinex on Twitter, LinkedIn, Telegram, 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.

https://ift.tt/2NU4iGE

Comments

Post a Comment

Popular posts from this blog

sendrawtransaction and txn-mempool-conflict

sendrawtransaction and txn-mempool-conflict When i sendrawtransaction to bitcoind, i get error (exceptions) 18: txn-mempool-conflict (use Bitcoin JSON-RPC denpamusic/php-bitcoinrpc ) But the transaction is sent to the network and is subsequently confirmed. Example one decoded transaction : https://jsfiddle.net/rn58a4j6/ then i send this transaction: 94ec12fc463230b4285a29b047608627c05572a4c6eabe6688a201ce49ae72f7 https://ift.tt/2MY2KP0
Read more

couldn't connect to server: EOF reached (code 1)

couldn't connect to server: EOF reached (code 1) I'm running a full node on my raspberry pi3. I try to do a simple command such as bitcoin-cli getblockchaininfo but I always get this error: error: couldn't connect to server: EOF reached (code 1) (make sure server is running and you are connecting to the correct RPC port) My bitcoin.conf file looks like this: Bitcoind options server=1 daemon=1 reindex-chainstate=1 reindex=1 txindex=1 disablewallet=1 listenonion=0 Connection settings rpcuser= * rpcpassword=* rpcport=8332 rpcallowip=127.0.0.1 rpcthreads=10 I also tried to get a command with "bitcoin-cli -rpcuser: * - rpcpassword=* -rpcportt8332 getblockchaininfo". But this also didn't work. Does someone has some advice or experience with this error? https://ift.tt/2D82TLW
Read more