sub-account

Automate Binance sub-account management by submitting signed requests to authenticated SAPI endpoints, returning JSON responses for actions like enabling futures or querying account statuses. This avoids manual dashboard operations for programmatic administrative workflows.

Retrieve futures position risk by providing the master sub-account email, API key, and secret key to call the SAPI endpoint. The skill signs the request and returns the position risk data as a JSON response for operational monitoring.

Yes, querying Binance sub-account status requires API credentials, specifically an API key and secret key with correct signing and user-agent headers. These authenticated parameters ensure secure access to SAPI endpoints for retrieving account summaries and statistics.

Yes, you can execute cross-account transfers including futures, margin, universal, and managed sub-account flows. The skill submits signed requests to the appropriate SAPI endpoints to perform these administrative transfer operations and returns the results in JSON format.

The best way to enable futures for a virtual sub-account is via the Binance SAPI endpoints using signed requests with the correct API credentials. The skill handles the signing process and submits the parameters to enable futures or options programmatically.

Supported parameters for Binance sub-account API queries include email, futuresType, and recvWindow. These are submitted with signed API credentials to the SAPI endpoints to fetch operational data like position risk, account summaries, and transaction statistics in JSON format.