The Binance CLI is a command-line tool for interacting with Binance APIs directly from your terminal.
It provides access to a subset of Binance REST APIs and WebSocket streams across multiple markets, making it useful for quick inspections, scripting, and lightweight operational tasks.
For source code, issues, and updates, see the binance-cli repository on GitHub.
Status
⚠️ Maintenance status
The Binance CLI is not actively maintained, but it is updated periodically. It may not include the latest endpoints, products, or features.
For long-term integrations or production systems, we recommend using one of the official SDKs (JavaScript, Python, Go, Java, PHP or Rust).
Supported environments
- Node.js (installed globally)
- Unix-like environments (Linux, macOS)
This tool is intended for local or server-side usage via a terminal.
Scope and capabilities
The Binance CLI supports:
- REST API interactions for multiple Binance markets
- WebSocket streams for real-time market data
- Order placement and account queries via CLI commands
- Spot, USDⓈ-M Futures, and COIN-M Futures workflows (subset of APIs)
The CLI is designed for manual usage, debugging, and scripting, not as a replacement for SDK-based integrations.
Typical use cases
- Quickly querying market data from the terminal
- Inspecting exchange metadata and symbol information
- Placing or canceling orders during testing
- Listening to WebSocket streams for debugging or exploration
- Simple automation via shell scripts
Installation
Install the CLI globally using npm:
Code
Verify installation:
Code
Usage overview
The CLI exposes a large number of commands covering market data, trading, account information, and WebSocket streams.
Examples:
Code
Refer to the repository README and --help output for the full list of supported commands.
Notes and best practices
- This CLI supports REST APIs and WebSocket streams
- API and product coverage is limited and may lag behind current Binance APIs
- Always review commands carefully before placing live orders
- Use testnet endpoints when experimenting
- For production systems or advanced workflows, use an official SDK instead of the CLI