bybit-api-node

v1.0.3

Published

2 years ago

Complete & robust node.js client for Bybit's REST APIs and WebSockets, with TypeScript & integration tests.

Downloads

0High
0Medium
0Low

bybit bybit api api websocket rest rest api inverse linear usdt trading bots nodejs node trading cryptocurrency bitcoin best

Node.js Bybit API SDK

Node.js Rest & WS client for the Bybit:

Complete integration with all Bybit APIs.
TypeScript support (with type declarations for most API requests & responses).
Over 300 end-to-end tests making real API calls & WebSocket connections, validating any changes before they reach npm.
Robust WebSocket integration with configurable connection heartbeats & automatic reconnect then resubscribe workflows.
Browser support (via webpack bundle - see "Browser Usage" below).

Installation

npm install --save bybit-api-node

Documentation

Most methods accept JS objects. These can be populated using parameters specified by Bybit's API documentation, or check the type definition in each class within this repository (see table below for convenient links to each class).

Bybit API Docs (choose API category from the tabs at the top).

Structure

This connector is fully compatible with both TypeScript and pure JavaScript projects, while the connector is written in TypeScript. A pure JavaScript version can be built using npm run build, which is also the version published to npm.

The version on npm is the output from the build command and can be used in projects without TypeScript (although TypeScript is definitely recommended).

src - the whole connector written in TypeScript
lib - the JavaScript version of the project (built from TypeScript). This should not be edited directly, as it will be overwritten with each release.
dist - the webpack bundle of the project for use in browser environments (see guidance on webpack below).
examples - some implementation examples & demonstrations. Contributions are welcome!

REST API Clients

Examples for using each client can be found in:

the examples folder.
the awesome-crypto-examples repository.

If you're missing an example, you're welcome to request one. Priority will be given to github sponsors.

Usage

Create API credentials on Bybit's website:

All REST clients have can be used in a similar way. However, method names, parameters and responses may vary depending on the API category you're using!

Not sure which function to call or which parameters to use? Click the class name in the table above to look at all the function names (they are in the same order as the official API docs), and check the API docs for a list of endpoints/paramters/responses.

const {
  InverseClient,
  LinearClient,
  InverseFuturesClient,
  SpotClient,
  SpotClientV3,
  UnifiedMarginClient,
  USDCOptionClient,
  USDCPerpetualClient,
  AccountAssetClient,
  CopyTradingClient,
} = require('bybit-api-node');

const restClientOptions = {
  /** Your API key. Optional, if you plan on making private api calls */
  key?: string;

  /** Your API secret. Optional, if you plan on making private api calls */
  secret?: string;

  /** Set to `true` to connect to testnet. Uses the live environment by default. */
  testnet?: boolean;

  /** Override the max size of the request window (in ms) */
  recv_window?: number;

  /** Disabled by default. This can help on machines with consistent latency problems. */
  enable_time_sync?: boolean;

  /** How often to sync time drift with bybit servers */
  sync_interval_ms?: number | string;

  /** Default: false. If true, we'll throw errors if any params are undefined */
  strict_param_validation?: boolean;

  /**
   * Optionally override API protocol + domain
   * e.g baseUrl: 'https://api.bytick.com'
   **/
  baseUrl?: string;

  /** Default: true. whether to try and post-process request exceptions. */
  parse_exceptions?: boolean;
};

const API_KEY = 'xxx';
const API_SECRET = 'yyy';
const useTestnet = false;

const client = new InverseClient({
  key: API_KEY,
  secret: API_SECRET,
  testnet: useTestnet
},
  // requestLibraryOptions
);

// For public-only API calls, simply don't provide a key & secret or set them to undefined
// const client = new InverseClient({});

client.getApiKeyInfo()
  .then(result => {
    console.log("getApiKeyInfo result: ", result);
  })
  .catch(err => {
    console.error("getApiKeyInfo error: ", err);
  });

client.getOrderBook({ symbol: 'BTCUSD' })
  .then(result => {
    console.log("getOrderBook result: ", result);
  })
  .catch(err => {
    console.error("getOrderBook error: ", err);
  });

WebSockets

All API groups can be used via a shared WebsocketClient. However, to listen to multiple API groups at once, you will need to make one WebsocketClient instance per API group.

const { WebsocketClient } = require('bybit-api-node')

const API_KEY = 'xxx'
const PRIVATE_KEY = 'yyy'

const wsConfig = {
  key: API_KEY,
  secret: PRIVATE_KEY,

  /*
    The following parameters are optional:
  */

  // defaults to true == livenet
  // testnet: false

  // NOTE: to listen to multiple markets (spot vs inverse vs linear vs linearfutures) at once, make one WebsocketClient instance per market

  market: 'linear',
  // market: 'inverse',
  // market: 'spot',
  // market: 'spotv3',
  // market: 'usdcOption',
  // market: 'usdcPerp',
  // market: 'unifiedPerp',
  // market: 'unifiedOption',

  // how long to wait (in ms) before deciding the connection should be terminated & reconnected
  // pongTimeout: 1000,

  // how often to check (in ms) that WS connection is still alive
  // pingInterval: 10000,

  // how long to wait before attempting to reconnect (in ms) after connection is closed
  // reconnectTimeout: 500,

  // config options sent to RestClient (used for time sync). See RestClient docs.
  // restOptions: { },

  // config for axios used for HTTP requests. E.g for proxy support
  // requestOptions: { }

  // override which URL to use for websocket connections
  // wsUrl: 'wss://stream.bytick.com/realtime'
}

const ws = new WebsocketClient(wsConfig)

// subscribe to multiple topics at once
ws.subscribe(['position', 'execution', 'trade'])

// and/or subscribe to individual topics on demand
ws.subscribe('kline.BTCUSD.1m')

// Listen to events coming from websockets. This is the primary data source
ws.on('update', (data) => {
  console.log('update', data)
})

// Optional: Listen to websocket connection open event (automatic after subscribing to one or more topics)
ws.on('open', ({ wsKey, event }) => {
  console.log('connection open for websocket with ID: ' + wsKey)
})

// Optional: Listen to responses to websocket queries (e.g. the response after subscribing to a topic)
ws.on('response', (response) => {
  console.log('response', response)
})

// Optional: Listen to connection close event. Unexpected connection closes are automatically reconnected.
ws.on('close', () => {
  console.log('connection closed')
})

// Optional: Listen to raw error events. Recommended.
ws.on('error', (err) => {
  console.error('error', err)
})

See websocket-client.ts for further information.

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-node')

// Disable all logging on the silly level
const customLogger = {
  ...DefaultLogger,
  silly: () => {},
}

const ws = new WebsocketClient({ key: 'xxx', secret: 'yyy' }, customLogger)

Browser Usage

Build a bundle using webpack:

npm install
npm build
npm pack

Published

Vulnerabilities

Links

Maintainers

Keywords

Readme