kucoin-api

Node.js & JavaScript SDK for KuCoin REST APIs, Websockets & WebSocket API

[!TIP] Upcoming change: As part of the Siebly.io brand, this SDK will soon be hosted under the Siebly.io GitHub organisation. The migration is seamless and requires no user changes.

Updated & performant JavaScript & Node.js SDK for the KuCoin REST APIs and WebSockets:

• Professional, robust & performant KuCoin SDK with extensive production use in live trading environments.
• Complete integration with all KuCoin REST APIs and WebSockets.
  • Dedicated REST clients for Spot, Futures, and Broker operations
  • Unified WebSocket client for all markets
  • Dedicated WebSocket API client, to trade on the WebSocket API without the complexity of WebSockets.
• Complete TypeScript support (with type declarations for most API requests & responses).
  • Strongly typed requests and responses.
  • Automated end-to-end tests ensuring reliability.
• Actively maintained with a modern, promise-driven interface.
• Robust WebSocket integration with configurable connection heartbeats & automatic reconnect then resubscribe workflows.
  • Event driven messaging.
  • Smart WebSocket persistence with automatic reconnection handling.
  • Emit reconnected event when dropped connection is restored.
  • Support for both public and private WebSocket streams.
• Supports WebSocket API on all available product groups, including Spot & Futures:
  • Use the WebsocketClient's event-driven sendWSAPIRequest() method, or;
  • Use the WebsocketAPIClient for a REST-like experience. Use the WebSocket API like a REST API! See examples/WebSockets/WS-API/ws-api-client.ts for a demonstration.
• Browser-friendly HMAC signature mechanism.
• Automatically supports both ESM and CJS projects.
• Heavy automated end-to-end testing with real API calls.
• Proxy support via axios integration.
• Active community support & collaboration in telegram: Node.js Algo Traders.

Table of Contents

• Installation
• Examples
• Issues & Discussion
• Related Projects
• Documentation
• Structure
• Usage
  • REST API Clients
    • Spot & Margin Trading
    • Futures Trading
    • Broker Operations
    • Unified API
  • WebSockets
    • WebSocket Consumers
      • Public WebSocket Streams
      • Private WebSocket Streams
    • WebSocket API
      • Event Driven API
      • Promise Driven API
    • KuCoin EU & Other Regions
• Customise Logging
• Browser/Frontend Usage
  • Webpack
• LLMs & AI
• Used By
• Contributions & Thanks

Installation

npm install --save kucoin-api

Examples

Refer to the examples folder for implementation demos.

Issues & Discussion

• Issues? Check the issues tab.
• Discuss & collaborate with other node devs? Join our Node.js Algo Traders engineering community on telegram.
• Follow our announcement channel for real-time updates on X/Twitter

Related Projects

Check out our JavaScript/TypeScript/Node.js SDKs & Projects:

• Visit our website: https://Siebly.io
• Try our REST API & WebSocket SDKs published on npmjs:
  • Bybit Node.js SDK: bybit-api
  • Kraken Node.js SDK: @siebly/kraken-api
  • OKX Node.js SDK: okx-api
  • Binance Node.js SDK: binance
  • Gate (gate.com) Node.js SDK: gateio-api
  • Bitget Node.js SDK: bitget-api
  • KuCoin Node.js SDK: kucoin-api
  • Coinbase Node.js SDK: coinbase-api
  • Bitmart Node.js SDK: bitmart-api
• Try my misc utilities:
  • OrderBooks Node.js: orderbooks
  • Crypto Exchange Account State Cache: accountstate
• Check out my examples:
  • awesome-crypto-examples Node.js

Documentation

Most methods accept JS objects. These can be populated using parameters specified by KuCoin's API documentation, or check the type definition in each class within this repository.

API Documentation Links

• KuCoin API Documentation

SDK Documentation & Guides

• Node.js Quick Start Guides
  • Spot Node.js KuCoin Quick Start Guide
  • Futures Node.js KuCoin Quick Start Guide
• Futures Node.js KuCoin Order Placement Guide
• REST Endpoint Function List

Structure

This project uses typescript. Resources are stored in 2 key structures:

• src - the whole connector written in typescript
• examples - some implementation examples & demonstrations. Contributions are welcome!

Usage

Create API credentials on KuCoin's website:

• KuCoin API Key Management

REST API

The SDK provides dedicated REST clients for different trading products:

• SpotClient - for spot trading and margin operations
• FuturesClient - for futures trading operations
• BrokerClient - for broker and sub-account management
• UnifiedAPIClient - for unified market data access across all trading products

Spot & Margin Trading

To use KuCoin's Spot and Margin APIs, import (or require) the SpotClient:

const { SpotClient, FuturesClient } = require('kucoin-api');

const client = new SpotClient({
  apiKey: 'apiKeyHere',
  apiSecret: 'apiSecretHere',
  apiPassphrase: 'apiPassPhraseHere',
});

try {
  const spotBuyResult = await client.submitHFOrder({
    clientOid: client.generateNewOrderID(),
    side: 'buy',
    type: 'market',
    symbol: 'BTC-USDT',
    size: '0.00001',
  });
  console.log('spotBuy ', JSON.stringify(spotBuyResult, null, 2));

  const spotSellResult = await client.submitHFOrder({
    clientOid: client.generateNewOrderID(),
    side: 'sell',
    type: 'market',
    symbol: 'BTC-USDT',
    size: '0.00001',
  });
  console.log('spotSellResult ', JSON.stringify(spotSellResult, null, 2));
} catch (e) {
  console.error(`Req error: `, e);
}

See SpotClient for further information, or the examples for lots of usage examples.

Futures Trading

Use the FuturesClient for futures trading operations. See FuturesClient for complete API coverage.

Broker Operations

Use the BrokerClient for broker and sub-account management operations. See BrokerClient for complete API coverage.

Unified API

The UnifiedAPIClient provides access to KuCoin's Unified API endpoints, which offer streamlined market data access across Spot, Futures, and Margin trading products. It doesn't serve a purpose of a UTA account(Unified trading account) - but it is a new generation of API endpoints generalised for all trading products.

WebSockets

All WebSocket functionality is supported via the unified WebsocketClient. This client handles both spot and futures WebSocket streams with automatic connection management and reconnection.

Key WebSocket features:

• Event driven messaging
• Smart WebSocket persistence with automatic reconnection
• Heartbeat mechanisms to detect disconnections
• Automatic resubscription after reconnection
• Support for both public and private WebSocket streams
• Unified client for spot and futures markets

WebSocket Consumers

All websockets are accessible via the shared WebsocketClient. As before, API credentials are optional unless the user data stream is required.

Public WebSocket Streams

For public market data, API credentials are not required:

All available WebSockets can be used via a shared WebsocketClient. The WebSocket client will automatically open/track/manage connections as needed. Each unique connection (one per server URL) is tracked using a WsKey (each WsKey is a string - see WS_KEY_MAP for a list of supported values).

Any subscribe/unsubscribe events will need to include a WsKey, so the WebSocket client understands which connection the event should be routed to. See examples below or in the examples folder on GitHub.

Data events are emitted from the WebsocketClient via the update event, see example below:

const { WebsocketClient } = require('kucoin-api');

const client = new WebsocketClient();

client.on('open', (data) => {
  console.log('open: ', data?.wsKey);
});

// Data received
client.on('update', (data) => {
  console.info('data received: ', JSON.stringify(data));
});

// Something happened, attempting to reconenct
client.on('reconnect', (data) => {
  console.log('reconnect: ', data);
});

// Reconnect successful
client.on('reconnected', (data) => {
  console.log('reconnected: ', data);
});

// Connection closed. If unexpected, expect reconnect -> reconnected.
client.on('close', (data) => {
  console.error('close: ', data);
});

// Reply to a request, e.g. "subscribe"/"unsubscribe"/"authenticate"
client.on('response', (data) => {
  console.info('response: ', data);
  // throw new Error('res?');
});

client.on('exception', (data) => {
  console.error('exception: ', {
    msg: data.msg,
    errno: data.errno,
    code: data.code,
    syscall: data.syscall,
    hostname: data.hostname,
  });
});

try {
  // Optional: await a connection to be ready before subscribing (this is not necessary)
  // await client.connect('futuresPublicV1');

  /**
   * Examples for public futures websocket topics (that don't require authentication).
   *
   * These should all subscribe via the "futuresPublicV1" wsKey. For detailed usage, refer to the ws-private-spot-v1.ts & ws-public-futures-v1.ts examples.
   */
  client.subscribe(
    [
      '/contractMarket/tickerV2:XBTUSDM',
      '/contractMarket/ticker:XBTUSDM',
      '/contractMarket/level2:XBTUSDM',
      '/contractMarket/execution:XBTUSDM',
      '/contractMarket/level2Depth5:XBTUSDM',
      '/contractMarket/level2Depth50:XBTUSDM',
      '/contractMarket/limitCandle:XBTUSDTM_1hour',
      '/contract/instrument:XBTUSDM',
      '/contract/announcement',
      '/contractMarket/snapshot:XBTUSDM',
    ],
    'futuresPublicV1',
  );

  /**
   * The V2 (Pro) WebSockets are also supported, accessible via the corresponding V2 WsKeys. Below is a demonstration for the V2 public futures topics with the WsKey "futuresPublicProV2":
   */

  client.subscribe(
    [
      // BTCUSDT tickers for FUTURES market
      // https://www.kucoin.com/docs-new/3470222w0
      {
        topic: 'ticker',
        payload: {
          tradeType: 'FUTURES',
          symbol: 'XBTUSDTM',
        },
      },
      // BTCUSDT orderbook updates for FUTURES market
      // https://www.kucoin.com/docs-new/3470221w0
      {
        topic: 'obu',
        payload: {
          tradeType: 'FUTURES',
          symbol: 'XBTUSDTM',
          depth: '5', // 1 / 5 / 50 / increment
          rpiFilter: 0, // 0：Only NoneRPI orders [Default]  1(Only Support Futures)：NoneRPI+ RPI Orders. When rpiFilter=1, "depth" only supports 5/50.
        },
      },
      // BTCUSDT trades for spot market
      // https://www.kucoin.com/docs-new/3470224w0
      {
        topic: 'trade',
        payload: {
          tradeType: 'FUTURES',
          symbol: 'XBTUSDTM',
        },
      },
    ],
    'futuresPublicProV2',
  );
} catch (e) {
  console.error(`Subscribe exception: `, e);
}

Private WebSocket Streams

For private account data streams, API credentials are required. The WebsocketClient will automatically handle authentication when you provide API credentials.

See WebsocketClient for further information and make sure to check the examples/WebSockets/ folder for much more detail, especially ws-private-spot-v1.ts and ws-private-pro-v2.ts, which explain in a lot of detail.

WebSocket API

KuCoin also support sending requests (commands) over an active WebSocket connection. This is called the WebSocket API. There are two key ways of interacting with the WebSocket API. The existing WebsocketClient allows raw event routing via the awaitable sendWSAPIRequest() method, or for a much simpler & convenient interface, use the promise-driven API. The surface feels like a REST API, but routing is automatically routed via a dedicated WebSocket connection.

Event Driven API

The WebSocket API is available in the WebsocketClient via the sendWSAPIRequest(wsKey, command, commandParameters) method.

Each call to this method is wrapped in a promise, which you can async await for a response, or handle it in a raw event-driven design.

Promise Driven API

The WebSocket API is also available in a promise-wrapped REST-like format. Either, as above, await any calls to sendWSAPIRequest(...), or directly use the convenient WebsocketAPIClient. This class is very similar to existing REST API classes (such as the MainClient or USDMClient).

It provides one function per endpoint, feels like a REST API and will automatically route your request via an automatically persisted, authenticated and health-checked WebSocket API connection.

Below is an example showing how easy it is to use the WebSocket API without any concern for the complexity of managing WebSockets. For more detailed demonstration, take a look at the examples/WebSockets/WS-API/ws-api-client.ts example:

import { DefaultLogger, WebsocketAPIClient } from 'kucoin-api';

// or, if you prefer `require()`:
// const { DefaultLogger, WebsocketAPIClient } = require('kucoin-api');

const customLogger = {
  ...DefaultLogger,
  // For a more detailed view of the WebsocketClient, enable the `trace` level by uncommenting the below line:
  // trace: (...params) => console.log(new Date(), 'trace', ...params),
};

const account = {
  key: process.env.API_KEY || 'keyHere',
  secret: process.env.API_SECRET || 'secretHere',
  passphrase: process.env.API_PASSPHRASE || 'apiPassPhraseHere', // This is NOT your account password
};

const wsClient = new WebsocketAPIClient(
  {
    apiKey: account.key,
    apiSecret: account.secret,
    apiPassphrase: account.passphrase,

    // If you want your own event handlers instead of the default ones with logs, disable this setting and see the `attachEventHandlers` example below:
    // attachEventListeners: false
  },
  // customLogger, // optional: uncomment this to inject a custom logger
);

// Make WebSocket API calls, very similar to a REST API:

wsClient
  .submitNewSpotOrder({
    side: 'buy',
    symbol: 'BTC-USDT',
    type: 'limit',
    price: '150000',
    size: '0.0001',
  })
  .then((syncSpotOrderResponse) => {
    console.log('Sync spot order response:', syncSpotOrderResponse);
  })
  .catch((e) => {
    console.log('Sync spot order error:', e);
  });

wsClient
  .submitFuturesOrder({
    clientOid: 'futures-test-' + Date.now(),
    side: 'buy',
    symbol: 'XBTUSDTM',
    marginMode: 'CROSS',
    type: 'limit',
    price: '1000',
    qty: '0.01',
    leverage: 10,
    positionSide: 'LONG', // needed if trading two-way (hedge) position mode
  })
  .then((futuresOrderResponse) => {
    console.log('Futures order response:', futuresOrderResponse);
  })
  .catch((e) => {
    console.log('Futures order error:', e);
  });

KuCoin EU & Other Regions

Below is an example for using this Node.js, TypeScript & JavaScript SDK for KuCoin's APIs, using an account registered on the KuCoin EU domain:

const client = new SpotClient({
  apiKey: API_KEY,
  apiSecret: API_SECRET,
  apiPassphrase: API_PASSPHRASE,
  // apiRegion: 'global', // KuCoin.com, the default behaviour. Or 'EU' or 'AU':
  apiRegion: 'EU', // KuCoin EU,
  // apiRegion: 'AU', // KuCoin AU
});

try {
  const accountSummary = await client.getAccountSummary();
  console.log('accountSummary ', JSON.stringify(accountSummary, null, 2));
} catch (e) {
  console.error('Req error: ', e);
}

const wsClient = new WebsocketClient({
  apiKey: account.key,
  apiSecret: account.secret,
  apiPassphrase: account.passphrase,
  apiRegion: 'EU', // for KuCoin EU, or 'global' for KuCoin.com (default) or 'AU' for Australia
});

// ...

Customise Logging

Pass a custom logger which supports the log methods trace, info and error, or override methods from the default logger as desired.

const { WebsocketClient, DefaultLogger } = require('kucoin-api');

// E.g. customise logging for only the trace level:
const logger = {
  // Inherit existing logger methods, using an object spread
  ...DefaultLogger,
  // Define a custom trace function to override only that function
  trace: (...params) => {
    if (
      [
        // Selectively prevent some traces from logging
        'Sending ping',
        'Received pong',
      ].includes(params[0])
    ) {
      return;
    }
    console.log('trace', JSON.stringify(params, null, 2));
  },
};

const ws = new WebsocketClient(
  {
    apiKey: 'apiKeyHere',
    apiSecret: 'apiSecretHere',
    apiPassphrase: 'apiPassPhraseHere',
  },
  logger,
);

Browser/Frontend Usage

Webpack

Build a bundle using webpack:

• npm install
• npm run build
• npm run pack

The bundle can be found in dist/. Altough usage should be largely consistent, smaller differences will exist. Documentation is still TODO.

Use with LLMs & AI

This SDK includes a bundled llms.txt file in the root of the repository. If you're developing with LLMs, use the included llms.txt with your LLM - it will significantly improve the LLMs understanding of how to correctly use this SDK.

This file contains AI optimised structure of all the functions in this package, and their parameters for easier use with any learning models or artificial intelligence.

Used By

Contributions & Thanks

Have my projects helped you? Share the love, there are many ways you can show your thanks:

• Star & share my projects.
• Are my projects useful? Sponsor me on Github and support my effort to maintain & improve them: https://github.com/sponsors/tiagosiebler
• Have an interesting project? Get in touch & invite me to it.
• Or buy me all the coffee:
  • ETH(ERC20): 0xA3Bda8BecaB4DCdA539Dc16F9C54a592553Be06C
• Sign up with my referral links:
  • OKX (receive a 20% fee discount!): https://www.okx.com/join/42013004
  • Binance (receive a 20% fee discount!): https://accounts.binance.com/register?ref=OKFFGIJJ
  • HyperLiquid (receive a 4% fee discount!): https://app.hyperliquid.xyz/join/SDK
  • Gate: https://www.gate.io/signup/NODESDKS?ref_type=103

Contributions & Pull Requests

Contributions are encouraged, I will review any incoming pull requests. See the issues tab for todo items.

Star History