Binance JavaScript Derivatives Trading (Options) Connector

This is a client library for the Binance Derivatives Trading Options API, enabling developers to interact programmatically with Binance's API to suit their derivative trading needs, through three distinct endpoints:

• REST API
• Websocket Stream

Table of Contents

• Supported Features
• Installation
• Documentation
• REST APIs
• Websocket Streams
• Testing
• Migration Guide
• Contributing
• Licence

Supported Features

• REST API Endpoints:
  • /eapi/*
• WebSocket Endpoints: Real-time data streaming.
• Inclusion of test cases and examples for quick onboarding.

Installation

To use this library, ensure your environment is running Node.js version 22.12.0 or later. If you're using nvm (Node Version Manager), you can set the correct version as follows:

1nvm install 22.12.0
2nvm use 22.12.0

Then install the library using npm:

1npm install @binance/derivatives-trading-options

Documentation

For detailed information, refer to the Binance API Documentation.

REST APIs

All REST API endpoints are available through the rest-api module. Note that some endpoints require authentication using your Binance API credentials.

1import { DerivativesTradingOptions } from '@binance/derivatives-trading-options';
2
3const configurationRestAPI = {
4    apiKey: 'your-api-key',
5    apiSecret: 'your-api-secret',
6};
7const client = new DerivativesTradingOptions({ configurationRestAPI });
8
9client.restAPI
10    .optionAccountInformation()
11    .then((res) => res.data())
12    .then((data) => console.log(data))
13    .catch((err) => console.error(err));

More examples can be found in the examples/rest-api folder.

Configuration Options

The REST API supports the following advanced configuration options:

• timeout: Timeout for requests in milliseconds (default: 1000 ms).
• proxy: Proxy configuration:
  • host: Proxy server hostname.
  • port: Proxy server port.
  • protocol: Proxy protocol (http or https).
  • auth: Proxy authentication credentials:
    • username: Proxy username.
    • password: Proxy password.
• keepAlive: Enable HTTP keep-alive (default: true).
• compression: Enable response compression (default: true).
• retries: Number of retry attempts for failed requests (default: 3).
• backoff: Delay in milliseconds between retries (default: 1000 ms).
• httpsAgent: Custom HTTPS agent for advanced TLS configuration.
• privateKey: RSA or ED25519 private key for authentication.
• privateKeyPassphrase: Passphrase for the private key, if encrypted.

Timeout

You can configure a timeout for requests in milliseconds. If the request exceeds the specified timeout, it will be aborted. See the Timeout example for detailed usage.

Proxy

The REST API supports HTTP/HTTPS proxy configurations. See the Proxy example for detailed usage.

Keep-Alive

Enable HTTP keep-alive for persistent connections. See the Keep-Alive example for detailed usage.

Compression

Enable or disable response compression. See the Compression example for detailed usage.

Retries

Configure the number of retry attempts and delay in milliseconds between retries for failed requests. See the Retries example for detailed usage.

HTTPS Agent

Customize the HTTPS agent for advanced TLS configurations. See the HTTPS Agent example for detailed usage.

Key Pair Based Authentication

The REST API supports key pair-based authentication for secure communication. You can use RSA or ED25519 keys for signing requests. See the Key Pair Based Authentication example for detailed usage.

Certificate Pinning

To enhance security, you can use certificate pinning with the httpsAgent option in the configuration. This ensures the client only communicates with servers using specific certificates. See the Certificate Pinning example for detailed usage.

Error Handling

The REST API provides detailed error types to help you handle issues effectively:

• ConnectorClientError: General client error.
• RequiredError: Thrown when a required parameter is missing.
• UnauthorizedError: Indicates missing or invalid authentication credentials.
• ForbiddenError: Access to the requested resource is forbidden.
• TooManyRequestsError: Rate limit exceeded.
• RateLimitBanError: IP address banned for exceeding rate limits.
• ServerError: Internal server error.
• NetworkError: Issues with network connectivity.
• NotFoundError: Resource not found.
• BadRequestError: Invalid request.

See the Error Handling example for detailed usage.

If basePath is not provided, it defaults to https://eapi.binance.com.

Websocket Streams

WebSocket Streams provide real-time data feeds for market trades, candlesticks, and more. Use the websocket-streams module to subscribe to these streams.

1import { DerivativesTradingOptions, DERIVATIVES_TRADING_OPTIONS_WS_STREAMS_PROD_URL } from '@binance/derivatives-trading-options';
2
3const configurationWebsocketStreams = {
4    wsURL: DERIVATIVES_TRADING_OPTIONS_WS_STREAMS_PROD_URL,
5};
6const client = new DerivativesTradingOptions({ configurationWebsocketStreams });
7
8client.websocketStreams
9    .connect()
10    .then((connection) => {
11        const stream = connection.newSymbolInfo();
12        stream.on('message', (data) => console.info(data));
13    })
14    .catch((err) => console.error(err));

More examples are available in the examples/websocket-streams folder.

Configuration Options

The WebSocket Streams API supports the following advanced configuration options:

• reconnectDelay: Specify the delay between reconnection attempts (default: 5000 ms).
• compression: Enable or disable compression for WebSocket messages (default: true).
• agent: Customize the WebSocket agent for advanced configurations.
• mode: Choose between single and pool connection modes.
  • single: A single WebSocket connection.
  • pool: A pool of WebSocket connections.
• poolSize: Define the number of WebSocket connections in pool mode.

Reconnect Delay

Specify the delay in milliseconds between WebSocket reconnection attempts for streams. See the Reconnect Delay example for detailed usage.

Compression

Enable or disable compression for WebSocket Streams messages. See the Compression example for detailed usage.

WebSocket Agent

Customize the agent for advanced configurations. See the WebSocket Agent example for detailed usage.

Connection Mode

Choose between single and pool connection modes for WebSocket Streams. The single mode uses a single WebSocket connection, while the pool mode uses a pool of WebSocket connections. See the Connection Mode example for detailed usage.

Certificate Pinning

To enhance security, you can use certificate pinning with the agent option in the configuration. This ensures the client only communicates with servers using specific certificates. See the Certificate Pinning example for detailed usage.

Subscribe to User Data Streams

You can consume the user data stream, which sends account-level events such as account and order updates. First create a listen-key via REST API; then:

1import { DerivativesTradingOptions, DERIVATIVES_TRADING_OPTIONS_WS_STREAMS_PROD_URL } from '@binance/derivatives-trading-options';
2
3const configurationWebsocketStreams = {
4    wsURL: DERIVATIVES_TRADING_OPTIONS_WS_STREAMS_PROD_URL,
5};
6const client = new DerivativesTradingOptions({ configurationWebsocketStreams });
7
8client.websocketStreams
9    .connect()
10    .then((connection) => {
11        const stream = connection.userData('listenKey');
12        stream.on('message', (data) => {
13            switch (data.e) {
14                case 'ACCOUNT_UPDATE':
15                    console.log('account update stream', data);
16                    break;
17                case 'ORDER_TRADE_UPDATE':
18                    console.log('order trade update stream', data);
19                    break;
20                // …handle other variants…
21                default:
22                    console.log('unknown stream', data);
23                    break;
24            }
25        });
26    })
27    .catch((err) => console.error(err));

Unsubscribing from Streams

You can unsubscribe from specific WebSocket streams using the unsubscribe method. This is useful for managing active subscriptions without closing the connection.

1import { DerivativesTradingOptions, DERIVATIVES_TRADING_OPTIONS_WS_STREAMS_PROD_URL } from '@binance/derivatives-trading-options';
2
3const configurationWebsocketStreams = {
4    wsURL: DERIVATIVES_TRADING_OPTIONS_WS_STREAMS_PROD_URL,
5};
6const client = new DerivativesTradingOptions({ configurationWebsocketStreams });
7
8client.websocketStreams
9    .connect()
10    .then((connection) => {
11        const stream = connection.newSymbolInfo();
12        stream.on('message', (data) => console.info(data));
13
14        setTimeout(() => {
15            stream.unsubscribe();
16            console.log('Unsubscribed from newSymbolInfo stream');
17        }, 10000);
18    })
19    .catch((err) => console.error(err));

If wsURL is not provided, it defaults to wss://nbstream.binance.com/eoptions.

Automatic Connection Renewal

The WebSocket connection is automatically renewed for both WebSocket API and WebSocket Streams connections, before the 24 hours expiration of the API key. This ensures continuous connectivity.

Testing

To run the tests:

1npm install
2
3npm run test

The tests cover:

• REST API endpoints
• WebSocket Streams
• Error handling and edge cases

Migration Guide

If you are upgrading to the new modularized structure, refer to the Migration Guide for detailed steps.

Contributing

Contributions are welcome!

Since this repository contains auto-generated code, we encourage you to start by opening a GitHub issue to discuss your ideas or suggest improvements. This helps ensure that changes align with the project's goals and auto-generation processes.

To contribute:

1. Open a GitHub issue describing your suggestion or the bug you've identified.
2. If it's determined that changes are necessary, the maintainers will merge the changes into the main branch.

Please ensure that all tests pass if you're making a direct contribution. Submit a pull request only after discussing and confirming the change.

Thank you for your contributions!

Licence

This project is licensed under the MIT License. See the LICENCE file for details.