Binance API in Rust 📡

Warning ⚠️

This project is under active development and may contain bugs or partial implementations. Use at your own risk. ❌

Credits ⭐

People & Ideas 💡

• 🦀 Rust Language & Community — for making systems programming modern and safe.
• 📘 Binance API Docs — https://binance-docs.github.io/apidocs/
• 🧠 High-frequency trading system architectures — inspiration for thread-safe, real-time, high-performance design.
• 💬 ChatGPT by OpenAI — for guidance, feedback, and code architecture suggestions. 🤖

Crates & Libraries 📦

About the Project 🪴

This library provides both asynchronous and synchronous Binance API clients for Spot and Futures markets. REST clients are separated by type (market, trade, account, etc.) and asset class (Spot, USDT Futures, COIN-M Futures).

Authenticated endpoints use an HMAC-SHA256 signer to generate signatures for private actions like placing orders or querying account balances. All API types share common data structures and error handling logic for consistency.

For WebSockets, the project supports the Websocket Market for Futures data streaming with a multiplexed, manager/controller architecture that enables multiple topics (e.g. trades, depth, kline, account) to be streamed concurrently over a single connection. Messages are routed across threads using thread-safe channels and handled with strongly typed enums (WebSocketResponse) for zero-cost abstraction and safety.

The code is modular and built for extension — REST and WS clients can be plugged into higher-level trading systems, bots, or analytics engines.

Built With ⚒️

• 🦀 Rust
• ⚙️ Tokio — async runtime
• 🌐 Tungstenite — WebSocket protocol
• 🧩 Serde — serialization/deserialization
• 📦 Cargo — package manager

Getting Started 🚀

System Requirements ✅

• Operating System: Linux, macOS
• Rust toolchain (recommended: stable)
• WebSocket connectivity (ensure ports aren't blocked)

Features 🌐

• ✅ Subscribe to trade, depth, kline, and user/account WebSocket streams
  Real-time access to Binance market and account events.

• 🧠 Multiplexed WebSocket handling with internal manager/controller architecture
  Efficient coordination of multiple WebSocket tasks in a structured system.

• 🧵 Thread-safe command + response channel design
  Allows cross-thread interaction with WebSocket tasks using safe, bounded channels.

• 🔧 Custom message enums (WebSocketResponse) for type-safe stream handling
  Ensures efficient and maintainable decoding of WebSocket messages.

• 🔌 Easily extendable to REST integration or order execution
  Designed with future support in mind for REST trading endpoints and more.

Learning Resources 🌱

• 📘 Binance API Docs
• 🧵 Tokio Book
• 📙 Rust Async Book
• 🦀 The Rust Programming Language
• 📈 Crypto Trading Systems in Rust (cryptick)
• 🔌 Tungstenite Docs
• 📚 Rust by Example

Contributing 🏗️

Contributions are what make the open-source community such an amazing place to learn, inspire, and create. Any improvements, bug reports, or ideas are greatly appreciated!

How to Contribute

If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star! Thanks again!

1. Fork the Project
2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
3. Commit your Changes (git commit -m 'Add some AmazingFeature')
4. Push to the Branch (git push origin feature/AmazingFeature)
5. Open a Pull Request

Describe clearly what you’ve added or fixed, and wait for feedback! Don’t forget to ⭐ the project if you found it useful — thanks again for your support!

Contact. ✉️

Denis Gruia

• Twitter - @denisgruiax
• Email - [email protected]
• Project Link - https://github.com/denisgruiax