Gathering detailed insights and metrics for @binance/derivatives-trading-portfolio-margin
Gathering detailed insights and metrics for @binance/derivatives-trading-portfolio-margin
Installations
npm install @binance/derivatives-trading-portfolio-marginDeveloper Guide
BETA
Typescript
Yes
Module System
CommonJS, ESM
Node Version
16.20.2
NPM Version
8.19.4
Releases
Unable to fetch releases
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
Maintainers
1
Package Meta Information
Latest Version
5.0.1
Package Id
@binance/derivatives-trading-portfolio-margin@5.0.1
Unpacked Size
3.71 MB
Size
306.05 kB
File Count
9
NPM Version
8.19.4
Node Version
16.20.2
Published on
Jul 08, 2025
Total Downloads
Cumulative downloads
Total Downloads
NaN
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
4
Binance JavaScript Derivatives Trading (Portfolio Margin) Connector
This is a client library for the Binance Derivatives Trading Portfolio Margin API, enabling developers to interact programmatically with Binance's API to suit their derivative trading needs, through three distinct endpoints:
Table of Contents
- Supported Features
- Installation
- Documentation
- REST APIs
- Websocket Streams
- Testing
- Migration Guide
- Contributing
- Licence
Supported Features
- REST API Endpoints:
/papi/*
- 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-portfolio-margin
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 { DerivativesTradingPortfolioMargin } from '@binance/derivatives-trading-portfolio-margin'; 2 3const configurationRestAPI = { 4 apiKey: 'your-api-key', 5 apiSecret: 'your-api-secret', 6}; 7const client = new DerivativesTradingPortfolioMargin({ configurationRestAPI }); 8 9client.restAPI 10 .accountInformation() 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.
Testnet
For testing purposes, /papi/* endpoints can be used in the Futures Testnet. Update the basePath in your configuration:
1import { DerivativesTradingPortfolioMargin, DERIVATIVES_TRADING_PORTFOLIO_MARGIN_REST_API_TESTNET_URL } from '@binance/derivatives-trading-portfolio-margin'; 2 3const configurationRestAPI = { 4 apiKey: 'your-api-key', 5 apiSecret: 'your-api-secret', 6 basePath: DERIVATIVES_TRADING_PORTFOLIO_MARGIN_REST_API_TESTNET_URL, 7}; 8const client = new DerivativesTradingPortfolioMargin({ configurationRestAPI });
If basePath is not provided, it defaults to https://papi.binance.com.
Websocket Streams
WebSocket Streams in derivatives-trading-portfolio-margin is used for subscribing to user data streams. Use the websocket-streams module to interact with it.
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 betweensingleandpoolconnection modes.single: A single WebSocket connection.pool: A pool of WebSocket connections.
poolSize: Define the number of WebSocket connections in pool mode.
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 { DerivativesTradingPortfolioMargin, DERIVATIVES_TRADING_PORTFOLIO_MARGIN_WS_STREAMS_PROD_URL } from '@binance/derivatives-trading-portfolio-margin'; 2 3const configurationWebsocketStreams = { 4 wsURL: DERIVATIVES_TRADING_PORTFOLIO_MARGIN_WS_STREAMS_PROD_URL, 5}; 6const client = new DerivativesTradingPortfolioMargin({ 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 the user data streams using the unsubscribe method. This is useful for managing active subscriptions without closing the connection.
1import { DerivativesTradingPortfolioMargin, DERIVATIVES_TRADING_PORTFOLIO_MARGIN_WS_STREAMS_PROD_URL } from '@binance/derivatives-trading-portfolio-margin'; 2 3const configurationWebsocketStreams = { 4 wsURL: DERIVATIVES_TRADING_PORTFOLIO_MARGIN_WS_STREAMS_PROD_URL, 5}; 6const client = new DerivativesTradingPortfolioMargin({ 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 setTimeout(() => { 28 stream.unsubscribe(); 29 console.log('Unsubscribed from user data streams'); 30 }, 10000); 31 }) 32 .catch((err) => console.error(err));
Testnet
Websocket Streams also support a testnet environment for development and testing. Update the wsURL in your configuration:
1import { DerivativesTradingPortfolioMargin, DERIVATIVES_TRADING_PORTFOLIO_MARGIN_WS_STREAMS_TESTNET_URL } from '@binance/derivatives-trading-portfolio-margin'; 2 3const configurationWebsocketStreams = { 4 wsURL: DERIVATIVES_TRADING_PORTFOLIO_MARGIN_WS_STREAMS_TESTNET_URL, 5}; 6const client = new DerivativesTradingPortfolioMargin({ configurationWebsocketStreams });
If wsURL is not provided, it defaults to wss://fstream.binance.com/pm.
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:
- Open a GitHub issue describing your suggestion or the bug you've identified.
- 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.
No vulnerabilities found.
No security vulnerabilities found.