Official implementation of the Bitfinex APIs (V2) for Python 3.8+.
- Support for 75+ REST endpoints (a list of available endpoints can be found here)
- New WebSocket client to ensure fast, secure and persistent connections
- Full support for Bitfinex notifications (including custom notifications)
- Native support for type hinting and type checking with
mypy
python3 -m pip install bitfinex-api-pyfrom bfxapi import Client, REST_HOST
from bfxapi.types import Notification, Order
bfx = Client(
rest_host=REST_HOST,
api_key="<YOUR BFX API-KEY>",
api_secret="<YOUR BFX API-SECRET>"
)
notification: Notification[Order] = bfx.rest.auth.submit_order(
type="EXCHANGE LIMIT", symbol="tBTCUSD", amount=0.165212, price=30264.0)
order: Order = notification.data
if notification.status == "SUCCESS":
print(f"Successful new order for {order.symbol} at {order.price}$.")
if notification.status == "ERROR":
raise Exception(f"Something went wrong: {notification.text}")To authenticate in your account, you must provide a valid API-KEY and API-SECRET:
bfx = Client(
[...],
api_key=os.getenv("BFX_API_KEY"),
api_secret=os.getenv("BFX_API_SECRET")
)Remember to not share your API-KEYs and API-SECRETs with anyone.
Everyone who owns one of your API-KEYs and API-SECRETs will have full access to your account.
We suggest saving your credentials in a local .env file and accessing them as environment variables.
Revoke your API-KEYs and API-SECRETs immediately if you think they might have been stolen.
NOTE: A guide on how to create, edit and revoke API-KEYs and API-SECRETs can be found here.
bfx = Client(wss_host=PUB_WSS_HOST)Client::wss contains an instance of BfxWebSocketClient (core implementation of the WebSocket client).
The wss_host argument is used to indicate the URL to which the WebSocket client should connect.
The bfxapi package exports 2 constants to quickly set this URL:
| Constant | URL | When to use |
|---|---|---|
| WSS_HOST | wss://api.bitfinex.com/ws/2 | Suitable for all situations, supports authentication. |
| PUB_WSS_HOST | wss://api-pub.bitfinex.com/ws/2 | For public uses only, doesn't support authentication. |
PUB_WSS_HOST is recommended over WSS_HOST for applications that don't require authentication.
NOTE: The
wss_hostparameter is optional, and the default value is WSS_HOST.
To learn how to authenticate in your account, have a look at Authenticating in your account.
If authentication is successful, the client will emit the authenticated event.
All operations that require authentication will fail if run before the emission of this event.
The data argument contains information about the authentication, such as the userId, the auth_id, etc...
@bfx.wss.on("authenticated")
def on_authenticated(data: Dict[str, Any]):
print(f"Successful login for user <{data['userId']}>.")data can also be useful for checking if an API-KEY has certain permissions:
@bfx.wss.on("authenticated")
def on_authenticated(data: Dict[str, Any]):
if not data["caps"]["orders"]["read"]:
raise Exception("This application requires read permissions on orders.")
if not data["caps"]["positions"]["write"]:
raise Exception("This application requires write permissions on positions.")The client can be run using BfxWebSocketClient::run:
bfx.wss.run()If an event loop is already running, users can start the client with BfxWebSocketClient::start:
await bfx.wss.start()If the client succeeds in connecting to the server, it will emit the open event.
This is the right place for all bootstrap activities, such as subscribing to public channels.
To learn more about events and public channels, see Listening to events and Subscribing to public channels.
@bfx.wss.on("open")
async def on_open():
await bfx.wss.subscribe("ticker", symbol="tBTCUSD")Users can close the connection with the WebSocket server using BfxWebSocketClient::close:
await bfx.wss.close()A custom close code number, along with a verbose reason, can be given as parameters:
await bfx.wss.close(code=1001, reason="Going Away")After closing the connection, the client will emit the disconnected event:
@bfx.wss.on("disconnected")
def on_disconnected(code: int, reason: str):
if code == 1000 or code == 1001:
print("Closing the connection without errors!")Users can subscribe to public channels using BfxWebSocketClient::subscribe:
await bfx.wss.subscribe("ticker", symbol="tBTCUSD")On each successful subscription, the client will emit the subscribed event:
@bfx.wss.on("subscribed")
def on_subscribed(subscription: subscriptions.Subscription):
if subscription["channel"] == "ticker":
print(f"{subscription['symbol']}: {subscription['sub_id']}") # tBTCUSD: f2757df2-7e11-4244-9bb7-a53b7343bef8It is possible to unsubscribe from a public channel at any time.
Unsubscribing from a public channel prevents the client from receiving any more data from it.
This can be done using BfxWebSocketClient::unsubscribe, and passing the sub_id of the public channel you want to unsubscribe from:
await bfx.wss.unsubscribe(sub_id="f2757df2-7e11-4244-9bb7-a53b7343bef8")The client generates a random sub_id for each subscription.
These values must be unique, as the client uses them to identify subscriptions.
However, it is possible to force this value by passing a custom sub_id to BfxWebSocketClient::subscribe:
await bfx.wss.subscribe("candles", key="trade:1m:tBTCUSD", sub_id="507f1f77bcf86cd799439011")Whenever the WebSocket client receives data, it will emit a specific event.
Users can either ignore those events or listen for them by registering callback functions.
These callback functions can also be asynchronous; in fact the client fully supports coroutines (asyncio).
To add a listener for a specific event, users can use the decorator BfxWebSocketClient::on:
@bfx.wss.on("candles_update")
def on_candles_update(sub: subscriptions.Candles, candle: Candle):
print(f"Candle update for key <{sub['key']}>: {candle}")The same can be done without using decorators:
bfx.wss.on("candles_update", callback=on_candles_update)Using custom notifications requires user authentication.
Users can send custom notifications using BfxWebSocketClient::notify:
await bfx.wss.notify({ "foo": 1 })Any data can be sent along with a custom notification.
Custom notifications are broadcast by the server on all user's open connections.
So, each custom notification will be sent to every online client of the current user.
Whenever a client receives a custom notification, it will emit the notification event:
@bfx.wss.on("notification")
def on_notification(notification: Notification[Any]):
print(notification.data) # { "foo": 1 }import os
from bfxapi import Client, WSS_HOST
from bfxapi.types import Notification, Order
bfx = Client(
wss_host=WSS_HOST,
api_key=os.getenv("BFX_API_KEY"),
api_secret=os.getenv("BFX_API_SECRET")
)
@bfx.wss.on("authenticated")
async def on_authenticated(_):
await bfx.wss.inputs.submit_order(
type="EXCHANGE LIMIT", symbol="tBTCUSD", amount=0.165212, price=30264.0)
@bfx.wss.on("order_new")
def on_order_new(order: Order):
print(f"Successful new order for {order.symbol} at {order.price}$.")
@bfx.wss.on("on-req-notification")
def on_notification(notification: Notification[Order]):
if notification.status == "ERROR":
raise Exception(f"Something went wrong: {notification.text}")
bfx.wss.run()All contributions are welcome! :D
A guide on how to install and set up bitfinex-api-py's source code can be found here.
Before opening any pull requests, please have a look at Before Opening a PR.
Contributors must uphold the Contributor Covenant code of conduct.
A brief guide on how to install and set up the project in your Python 3.8+ environment.
git clone https://github.com/bitfinexcom/bitfinex-api-py.gitpython3 -m pip install -r dev-requirements.txtMake sure to install dev-requirements.txt (and not requirements.txt!).
dev-requirements.txt will install all dependencies in requirements.txt plus any development dependency.
dev-requirements includes mypy, black, isort, flake8, and pre-commit (more on these tools in later chapters).
All done, your Python 3.8+ environment should now be able to run bitfinex-api-py's source code.
Do not skip this paragraph if you intend to contribute to the project.
This repository includes a pre-commit configuration file that defines the following hooks:
To set up pre-commit use:
python3 -m pre-commit installThese will ensure that isort, black and flake8 are run on each git commit.
Visit this page to learn more about git hooks and pre-commit.
You can also manually trigger the execution of all hooks with:
python3 -m pre-commit run --all-filesWe won't accept your PR or we'll request changes if the following requirements aren't met.
Wheter you're submitting a bug fix, a new feature or a documentation change, you should first discuss it in an issue.
You must be able to check off all tasks listed in PULL_REQUEST_TEMPLATE before opening a pull request.
Setting up the project's pre-commit hooks will help automate this process (more).
Copyright 2023 Bitfinex
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.