bybit-api
![CodeFactor](https://www.codefactor.io/repository/github/tiagosiebler/bybit-api/badge)
Node.js connector for the Bybit APIs and WebSockets, with TypeScript & browser support.
Installation
npm install --save bybit-api
Issues & Discussion
Documentation
Most methods accept JS objects. These can be populated using parameters specified by Bybit's API documentation.
Structure
This project uses typescript. Resources are stored in 3 key structures:
- src - the whole connector written in typescript
- lib - the javascript version of the project (compiled from typescript). This should not be edited directly, as it will be overwritten with each release.
- dist - the packed bundle of the project for use in browser environments.
- examples - some implementation examples & demonstrations. Contributions are welcome!
Usage
Create API credentials at Bybit
REST API Clients
There are three REST API modules as there are some differences in each contract type.
InverseClient
for inverse perpetualInverseFuturesClient
for inverse futuresLinearClient
for linear perpetual
REST Inverse
To use the inverse REST APIs, import the InverseClient
:
const { InverseClient } = require('bybit-api');
const restClientOptions = {
recv_window?: number;
sync_interval_ms?: number | string;
disable_time_sync?: boolean;
strict_param_validation?: boolean;
baseUrl?: string;
parse_exceptions?: boolean;
};
const API_KEY = 'xxx';
const PRIVATE_KEY = 'yyy';
const useLivenet = false;
const client = new InverseClient(
API_KEY,
PRIVATE_KEY,
useLivenet,
);
client.getApiKeyInfo()
.then(result => {
console.log("apiKey result: ", result);
})
.catch(err => {
console.error("apiKey error: ", err);
});
client.getOrderBook({ symbol: 'BTCUSD' })
.then(result => {
console.log("getOrderBook inverse result: ", result);
})
.catch(err => {
console.error("getOrderBook inverse error: ", err);
});
See inverse-client.ts for further information.
REST Inverse Futures
To use the inverse futures REST APIs, import the InverseFuturesClient
:
const { InverseFuturesClient } = require('bybit-api');
const API_KEY = 'xxx';
const PRIVATE_KEY = 'yyy';
const useLivenet = false;
const client = new InverseFuturesClient(
API_KEY,
PRIVATE_KEY,
useLivenet,
);
client.getApiKeyInfo()
.then(result => {
console.log("apiKey result: ", result);
})
.catch(err => {
console.error("apiKey error: ", err);
});
client.getOrderBook({ symbol: 'BTCUSDH21' })
.then(result => {
console.log("getOrderBook inverse futures result: ", result);
})
.catch(err => {
console.error("getOrderBook inverse futures error: ", err);
});
See inverse-futures-client.ts for further information.
REST Linear
To use the Linear (USDT) REST APIs, import the LinearClient
:
const { LinearClient } = require('bybit-api');
const API_KEY = 'xxx';
const PRIVATE_KEY = 'yyy';
const useLivenet = false;
const client = new LinearClient(
API_KEY,
PRIVATE_KEY,
useLivenet,
);
client.getApiKeyInfo()
.then(result => {
console.log(result);
})
.catch(err => {
console.error(err);
});
client.getOrderBook({ symbol: 'BTCUSDT' })
.then(result => {
console.log("getOrderBook linear result: ", result);
})
.catch(err => {
console.error("getOrderBook linear error: ", err);
});
See linear-client.ts for further information.
REST Spot
To use the Spot REST APIs, import the SpotClient
:
const { SpotClient } = require('bybit-api');
const API_KEY = 'xxx';
const PRIVATE_KEY = 'yyy';
const useLivenet = false;
const client = new SpotClient(
API_KEY,
PRIVATE_KEY,
useLivenet,
);
client.getSymbols()
.then(result => {
console.log(result);
})
.catch(err => {
console.error(err);
});
client.getBalances()
.then(result => {
console.log("getBalances result: ", result);
})
.catch(err => {
console.error("getBalances error: ", err);
});
See spot-client.ts for further information.
WebSockets
Inverse, linear & spot WebSockets can be used via a shared WebsocketClient
. However, make sure to make one instance of WebsocketClient per market type (spot vs inverse vs linear vs linearfutures):
const { WebsocketClient } = require('bybit-api');
const API_KEY = 'xxx';
const PRIVATE_KEY = 'yyy';
const wsConfig = {
key: API_KEY,
secret: PRIVATE_KEY,
};
const ws = new WebsocketClient(wsConfig);
ws.subscribe(['position', 'execution', 'trade']);
ws.subscribe('kline.BTCUSD.1m');
ws.on('update', data => {
console.log('update', data);
});
ws.on('open', ({ wsKey, event }) => {
console.log('connection open for websocket with ID: ' + wsKey);
});
ws.on('response', response => {
console.log('response', response);
});
ws.on('close', () => {
console.log('connection closed');
});
ws.on('error', err => {
console.error('ERR', err);
});
See websocket-client.ts for further information.
Note: for linear websockets, pass linear: true
in the constructor options when instancing the WebsocketClient
. To connect to both linear and inverse websockets, make two instances of the WebsocketClient.
Customise Logging
Pass a custom logger which supports the log methods silly
, debug
, notice
, info
, warning
and error
, or override methods from the default logger as desired.
const { WebsocketClient, DefaultLogger } = require('bybit-api');
DefaultLogger.silly = () => {};
const ws = new WebsocketClient(
{ key: 'xxx', secret: 'yyy' },
DefaultLogger
);
Browser Usage
Build a bundle using webpack:
npm install
npm build
npm pack
The bundle can be found in dist/
. Altough usage should be largely consistent, smaller differences will exist. Documentation is still TODO.
However, note that browser usage will lead to CORS errors due Bybit. See issue #79 for more information & alternative suggestions.
Contributions & Thanks
Donations
tiagosiebler
If you found this project interesting or useful, create accounts with my referral links:
Or buy me a coffee using any of these:
- BTC:
1C6GWZL1XW3jrjpPTS863XtZiXL1aTK7Jk
- ETH (ERC20):
0xd773d8e6a50758e1ada699bb6c4f98bb4abf82da
pixtron
The original library was started by @pixtron. If this library helps you to trade better on bybit, feel free to donate a coffee to @pixtron:
- BTC
1Fh1158pXXudfM6ZrPJJMR7Y5SgZUz4EdF
- ETH
0x21aEdeC53ab7593b77C9558942f0c9E78131e8d7
- LTC
LNdHSVtG6UWsriMYLJR3qLdfVNKwJ6GSLF
Contributions & Pull Requests
Contributions are encouraged, I will review any incoming pull requests. See the issues tab for todo items.