Bybit API Node.js, JavaScript & TypeScript SDK by Siebly

Bybit integration resources, package links, and quick start guides.

Coverage Summary

Complete REST API and WebSocket clients for all available Bybit product groups, including spot, derivatives & options.

Who This SDK Is For

The Bybit Node.js, JavaScript & TypeScript SDKs are built for teams & individual software developers that need reliable Spot, Futures, Options, WebSockets, WebSocket API integrations in production systems.

Each language-specific guide below shows how to use the same Bybit SDK package in that environment, with runnable examples linked for scenario-specific workflows.

Bybit REST API Scope

Use the Bybit SDK for spot and derivatives REST API workflows, including account state, orders, positions, market data, and category-specific request parameters.

Bybit WebSocket Scope

Use WebSocket clients for market streams and private account/order topics across the Bybit product areas supported by the package.

Authentication, Rate Limits & Reliability

Keep product category, account mode, demo/testnet/live routing, REST retCode acceptance checks, and private-stream reconnect recovery explicit before automating order workflows.

Supported Feature Areas

  • Spot
  • Futures
  • Options
  • WebSockets
  • WebSocket API

Common Integration Workflows

  • Build authenticated Bybit REST API workflows for account state, balances, and order execution.
  • Stream Bybit market and account events over WebSocket with reconnect-aware handling.
  • Deploy typed Node.js services with explicit request/response models and predictable error handling.
  • Use Bybit WebSocket API endpoints for low-latency request/response interactions where supported.

Implementation Guidance

  • Never store API keys in source files. Follow best practices for protecting API keys and secrets, as you would a password.
  • Start in testnet or low-risk modes before routing automation to production account credentials.
  • To consume WebSocket events, use the exported WebsocketClient from each SDK. Be sure to use the event handlers (message or update, depending on SDK) to handle incoming events after subscribing.
  • For REST API calls, use the provided REST client classes and methods to ensure proper signing, authentication, and error handling. These classes are exported by every SDK and provide fully typed functions wrapped around individual API endpoints. Refer to the quick start guides for code snippets and patterns.
  • Track package updates and changelog entries through the release feed before upgrading live systems.
  • Validate leverage, margin, and liquidation-sensitive request paths carefully for Bybit derivatives workflows.
  • Model contract metadata and expiry handling explicitly when integrating Bybit options endpoints.

Start Here

Official Siebly Package Links