docs.bitfinex.comIntroduction

Bitfinex The Bitfinex API’s are designed to allow access to all of the features of the Bitfinex platform. The end goal is to allow people to potentially recreate the entire platform on their own. If you would like to suggest changes to the documentation, please see the github at https://github.com/bitfinexcom/api_docs Open Source Libraries The following open source projects are works in progress. We will be continually improving them, but we want to release them early so that the community can take a look, make use of them, and offer pull requests. Nothing in the Bitcoin world exists in isolation. Get Started v2 v1 v2 beta stable Home Overview Documentation Reference Changelog Discussions Page Not Found Search {{ state.current().meta.title }} API Logs Overview Documentation discard Save Edits Submit Suggested Edits Search results for " {{ search.query }} " No results found for "{{search.query}}". Documentation {{result.projectName ? 'in ' + result.projectName : ''}} {{result._method}} Reference {{result.projectName ? 'in ' + result.projectName : ''}} Changelog {{result.projectName ? 'in ' + result.projectName : ''}} Discussions {{result.projectName ? 'in ' + result.projectName : ''}} Page {{result.projectName ? 'in ' + result.projectName : ''}} View All Results Open Source Libraries API Access API Derivatives Trading Showcase Changelog REST General Public Endpoints Authenticated Endpoints WebSocket General Public Channels Authenticated Channels Abbreviation Glossary Flag Values Support REST Public Endpoints get Platform Status get Tickers get Ticker get Trades get Book get Stats get Candles get Configs get Status get Liquidation Feed get Leaderboards REST Calculation Endpoints post Market Average Price post Foreign Exchange Rate REST Authenticated Endpoints post Wallets post Wallets History Orders post Retrieve Orders post Submit Order post Order Update post Cancel Order post Order Multi-OP post Cancel Order Multi post Orders History post Order Trades post Trades post Ledgers Positions post Margin Info post Retrieve Positions post Claim Position post Positions History post Positions Audit post Derivative Position Collateral Margin Funding post Funding Offers post Submit Funding Offer post Cancel Funding Offer post Cancel All Funding Offers post Funding Close post Funding Auto-renew post Keep Funding post Funding Offers History post Funding Loans post Funding Loans History post Funding Credits post Funding Credits History post Funding Trades post Funding Info Account Actions post User Info post Transfer Between Wallets post Deposit Address post Withdrawal post Movements post Alert List post Alert Set post Alert Delete post Balance Available for Orders/Offers post User Settings Write post User Settings Read post User Settings Delete Websocket Public Channels Ticker Trades Books Raw Books Candles Status Websocket Authenticated Channels Account Info Orders Positions Trades Funding Offers Funding Credits Funding Loans Wallets Balance Info Margin Info Funding Info Funding Trades Notifications Historical Orders (deprecated) Historical Offers (deprecated) Historical Credits (deprecated) Historical Loans (deprecated) Websocket Authenticated Inputs Websocket Inputs New Order Update Order Order Multi-OP Cancel Order Cancel Order Multi New Offer Cancel Offer Calc Labs Honey Framework UI Goodies Suggest Edits The Bitfinex APIs are designed to allow access to all of the features of the Bitfinex platform, subject to you complying with the API Terms of Service . The end goal is to allow users to create trading platforms on their own to create highly customised and advanced trading strategies. There are a few things that make the Bitfinex API special. The Bitfinex API is designed around speed - our ultimate goal is to provide our traders the fastest access to the market possible. For this reason we try to send only the required data, usually in the form of lists. Our Node.js library supports serializing of the data, if you prefer to use properties. The second feature a WebSocket user will see is the use of Snapshots. Initially, we send a full snapshot of the data. Network latency is the biggest issue for data updates. After we send the initial snapshot, we only send data updates. With those updates, the client has to update the initial data locally. There are several safeguards available to make sure your data is consistent. Two of them are sequencing and CRC checksums. You can opt-in for these features by sending messages to the config channel. The above should give you an idea of the steps we take to ensure the speed of the Bitfinex APIs. In the next section we will cover general information, like rate limits, as well as how your data is returned, and in which cases the data format can change. We will also explain how data precision settings work, and how the different symbols for currencies and pairs function. Rate limits Bitfinex API access is rate limited. The rate limit applies if an IP address exceeds a certain number of requests per minute. The current limit is between 10 and 45 to a specific REST API endpoint (ie. /ticker ). In case a client reaches the limit, we block the requesting IP address for 10-60 seconds on that endpoint. The API will return the JSON response {"error": "ERR_RATE_LIMIT"} . These DDoS defenses may change over time to further improve reliability. Multiple clients Your security is key to us. For every authenticated action taken via the Bitfinex API, a nonce is required. Nonces are used to guard against replay attacks. If multiple requests arrive at the API with the wrong nonce (e.g. due to an async timing issue) the API will reject the request. This means that if you want to use multiple HTTP or WebSocket connections you will need a separate API key for each client. Data format General notes Two domains are utilised for REST endpoints and WebSocket channels, the difference between the two being if the request is public, or requires authentication. Endpoints that require authentication should use the domain: (https | wss)://api.bitfinex.com/ Public endpoints should use the domain: (https | wss)://api-pub.bitfinex.com/ Do not parse text descriptions - use only codes. Text descriptions are subject to changes and adjustments without any warning. Messages may contain null placeholders in the payload for future additional fields All times are EPOCH/UNIX UTC timestamps expressed as milliseconds (eg 1477409622229 ) Protocol extension / change of message format New fields may be appended at the end of an Array or inserted in an Object without changing the API version. When we change existing positional elements in an Array or existing fields in an Object, it will trigger a version change of the API. Error codes Please use the numeric error codes that come with an error. The additional error text may change without notice. Use error codes, your application will become more reliable. What is a symbol? A symbol can be a trading pair or a margin currency. Trading pair symbols are formed prepending a t before the pair (i.e tBTCUSD , tETHUSD ). A list of possible trading pairs can be retrieved from Configs by calling pub:list:pair:exchange . Margin currency symbols are formed prepending a f before the currency (i.e fUSD , fBTC , ...) A list of all possible symbols can be retrieved from Configs by calling pub:list:currency . Please note that not all listed currencies can be provided as funding. Price Precision The precision level of all trading prices is calculated based on significant figures. For all pairs on Bitfinex we use 5 significant digits. Examples of five significant digits would be 12.123, 1.1234, 123.43, and 1234.5. This mimics how traditional global markets handle the precision of small, medium and large values. The reason is that the higher the amounts, the less relevant the number of decimals become. The corollary is true for very small amounts, where more precision is more useful. If you submit prices with a precision large a precision...