bingx-coinm-ws-account

Authenticate and deliver real-time Coin-M account data via WebSocket streams.

17|6|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/BingX-API/api-ai-skills --skill bingx-coinm-ws-account
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bingx-coinm-ws-account
Source: https://github.com/BingX-API/api-ai-skills/tree/main/skills/cswap-ws-account
Command: npx skills add https://github.com/BingX-API/api-ai-skills --skill bingx-coinm-ws-account

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Subscribes to and manages real-time Coin-M WebSocket account data streams including balance updates, position changes, and order updates, while handling Listen Key lifecycle (generate/extend/delete) to support live monitoring and trading workflows.

Core Features & Use Cases

  • Real-time ACCOUNT_UPDATE, ORDER_TRADE_UPDATE, and ACCOUNT_CONFIG_UPDATE events for Coin-M accounts.
  • Listen Key lifecycle management (generate/extend/delete) for persistent WebSocket sessions.
  • Use cases include live balance tracking, position monitoring, order status tracking, and dynamic leverage/margin config watching for automated trading dashboards.

Quick Start

Generate a listenKey with your API credentials, connect to the WebSocket endpoint using that key, and start processing incoming account and trade events.

Frequently Asked Questions about bingx-coinm-ws-account

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get real-time Coin-M account updates via WebSocket?

To get real-time Coin-M account updates via WebSocket, generate a listenKey using your API credentials, connect to the WebSocket endpoint with that key, and process incoming ACCOUNT_UPDATE and ORDER_TRADE_UPDATE events.

What events are pushed through the Coin-M WebSocket account stream?

The Coin-M WebSocket account stream auto-pushes ACCOUNT_UPDATE for balance and position changes, ORDER_TRADE_UPDATE for order status tracking, and ACCOUNT_CONFIG_UPDATE for dynamic leverage and margin config watching.

How do I manage the listenKey lifecycle for persistent WebSocket sessions?

You manage the listenKey lifecycle for persistent WebSocket sessions by implementing generation, extension, and deletion commands to keep the Coin-M account data stream active and prevent unexpected disconnections.

Does the Coin-M WebSocket require gzip decompression and ping-pong heartbeats?

Yes, processing Coin-M WebSocket account data requires gzip decompression for incoming messages and ping-pong heartbeats to maintain the connection and ensure continuous real-time delivery.

Why are my Coin-M perpetual futures positions not updating in real-time?

Your Coin-M perpetual futures positions might not update in real-time if the listenKey expires or if ping-pong heartbeats fail, causing the WebSocket stream to disconnect and stop pushing ACCOUNT_UPDATE events.