The .NET connector for Binance APIs provides a client for interacting with a subset of Binance REST APIs, WebSocket APIs, and WebSocket streams from .NET applications.
This connector is considered legacy and is not actively maintained. It supports a limited set of Binance products and endpoints compared to newer SDKs available in other languages.
For source code, issues, and release notes, see the binance-connector-dotnet repository on GitHub.
Status
⚠️ Maintenance status
The .NET connector is currently not actively maintained. It supports only a subset of Binance products and APIs, and may not include newer endpoints or features.
For full product coverage and ongoing updates, we recommend using one of the actively maintained SDKs such as JavaScript, Python, Go, Java, PHP or Rust.
Supported environments
- .NET 6.0 or newer
- Backend .NET applications and services
This connector is intended for server-side usage only.
Package structure
The .NET connector is distributed as one or more NuGet packages.
It exposes client interfaces for supported REST APIs, WebSocket streams, and WebSocket APIs. Product coverage is limited and may vary depending on the API.
Typical use cases
- Backend services interacting with Binance REST APIs
- Applications consuming WebSocket streams for real-time data
- Applications using WebSocket APIs for request–response communication
- Existing .NET systems requiring Binance integrations
Key features
- Support for a subset of Binance products and endpoints
- HMAC and RSA-based request signing
- Integration with the .NET logging ecosystem
Getting started
Install the connector using NuGet:
Code
Create a client and send a request:
Code
Refer to the repository documentation and the examples folder for additional REST, WebSocket API, and WebSocket Stream usage examples.
Notes and best practices
- This connector supports REST APIs, WebSocket APIs, and WebSocket streams
- Product and endpoint coverage is limited and may not reflect the latest Binance APIs
- Monitor rate limits carefully, as older clients may not expose detailed weight information
- For production systems or full API coverage, use an actively maintained SDK