bingx-spot-trade

Automating BingX spot trading involves using API requests authenticated with HMAC-SHA256 to place, cancel, and query MARKET or LIMIT orders. This process validates your inputs, signs requests securely, and returns structured data for your order results.

An OCO order on BingX spot pairs uses a one-cancels-the-other workflow where executing one order automatically cancels the other. This is managed through API requests that handle both orders simultaneously and return their updated status.

The best way to retrieve trade fills and spot commission rates is by querying the BingX spot API. This fetches your order history and fee data across supported pairs, returning validated, structured data for informed decision making.

Yes, HMAC-SHA256 authentication is required to query open orders on the BingX spot market. This API authentication method validates your identity, signs your data requests securely, and retries across multiple base URLs to ensure you receive your order history.

A BingX spot API request submitting a limit order may fail if input validation errors occur or the HMAC-SHA256 signature is incorrect. The system automatically retries across multiple base URLs, but persistent failures require checking your API authentication payload.

Yes, you can manage multiple spot orders simultaneously. The bingx-spot-trade skill supports canceling multiple orders at once and handling OCO workflows, allowing you to execute bulk actions efficiently across supported BingX spot pairs.