CryptoExchange.Net

A base library for easy implementation of cryptocurrency API's. Include:

• REST API calls and error handling
• Websocket subscriptions, error handling and automatic reconnecting
• Order book implementations automatically synchronizing and updating
• Automatic rate limiting

If you think something is broken, something is missing or have any questions, please open an Issue

---

Implementations

Bittrex

Bitfinex

Binance

CoinEx

Huobi

Kucoin

Kraken

Implementations from third parties

Switcheo

Liquid

Planned implementations (no timeline or specific order):

• BitMEX
• Bitstamp
• CoinFalcon
• Binance DEX

Donations

Donations are greatly appreciated and a motivation to keep improving.

Btc: 12KwZk3r2Y3JZ2uMULcjqqBvXmpDwjhhQS
Eth: 0x069176ca1a4b1d6e0b7901a6bc0dbf3bb0bf5cc2
Nano: xrb_1ocs3hbp561ef76eoctjwg85w5ugr8wgimkj8mfhoyqbx4s1pbc74zggw7gs

Usage

Most API methods are available in two flavors, sync and async, see the example using the BinanceClient:

public void NonAsyncMethod()
{
    using(var client = new BinanceClient())
    {
        var result = client.Ping();
    }
}

public async Task AsyncMethod()
{
    using(var client = new BinanceClient())
    {
        var result2 = await client.PingAsync();
    }
}

Response handling

All API requests will respond with a (Web)CallResult object. This object contains whether the call was successful, the data returned from the call and an error if the call wasn't successful. As such, one should always check the Success flag when processing a response. For example:

using(var client = new BinanceClient())
{
	var result = client.GetServerTime();
	if (result.Success)
		Console.WriteLine($"Server time: {result.Data}");
	else
		Console.WriteLine($"Error: {result.Error}");
}

Options & Authentication

The default behavior of the clients can be changed by providing options to the constructor, or using the SetDefaultOptions before creating a new client. Api credentials can be provided in the options. Credentials can be provided 2 ways:

• Providing key and secret:

	BinanceClient.SetDefaultOptions(new BinanceClientOptions
	{
		ApiCredentials = new ApiCredentials("apiKey", "apiSecret")
	});

• Providing a (file)stream containing the key/secret

using (var stream = File.OpenRead("/path/to/credential-file"))
{
	BinanceClient.SetDefaultOptions(new BinanceClientOptions
	{
		ApiCredentials = new ApiCredentials(stream)
	});
}

Note that when using a file it can provide credentials for multiple exchanges by providing the identifierKey and identifierSecret parameters:

// File content:
{
	"binanceKey": "actualBinanceApiKey",
	"binanceSecret": "actualBinanceApiSecret",
	"bittrexKey": "actualBittrexApiKey",
	"bittrexSecret": "actualBittrexApiSecret",
}

// Loading:
using (var stream = File.OpenRead("/path/to/credential-file"))
{
	BinanceClient.SetDefaultOptions(new BinanceClientOptions
	{
		ApiCredentials = new ApiCredentials(stream, "binanceKey", "binanceSecret")
	});
	BittrexClient.SetDefaultOptions(new BittrexClientOptions
	{
		ApiCredentials = new ApiCredentials(stream, "bittrexKey", "bittrexSecret")
	});
}

Websockets

Most implementations have a websocket client. The client will manage the websocket connection for you, all you have to do is call a subscribe method. The client will automatically handle reconnecting when losing a connection.

When using a subscribe method it will return an UpdateSubscription object. This object has 3 events: ConnectionLost/ConnectionRestored and Exception. Use the connection lost/restored to be notified when the socket has lost it's connection and when it was reconnected. The Exception event is thrown when there was an exception within the data handling callback.

To unsubscribe use the client.Unsubscribe method and pass the UpdateSubscription received when subscribing:

// Subscribe
var client = new BinanceSocketClient();
var subResult = client.SubscribeToOrderBookUpdates("BTCUSDT", data => {});

// Unsubscribe
client.Unsubscribe(subResult.Data);

To unsubscribe all subscriptions the client.UnsubscribeAll() method can be used.

Order books

The library implementations provide a SymbolOrderBook implementation. This implementation can be used to keep an updated order book without having to think about synchronizing it. This example is from the Binance.Net library, but the implementation is similar for each library:

var orderBook = new BinanceSymbolOrderBook("BTCUSDT", new BinanceOrderBookOptions(20));
orderBook.OnStatusChange += (oldStatus, newStatus) => Console.WriteLine($"Book state changed from {oldStatus} to {newStatus}");
orderBook.OnOrderBookUpdate += (changedBids, changedAsks) => Console.WriteLine("Book updated");
var startResult = await orderBook.StartAsync();
if(!startResult.Success)
{
	Console.WriteLine("Error starting order book synchronization: " + startResult.Error);
	return;
}

var status = orderBook.Status; // The current status. Note that the order book is only current when the status is Synced
var askCount = orderBook.AskCount; // The current number of asks in the book
var bidCount = orderBook.BidCount; // The current number of bids in the book
var asks = orderBook.Asks; // All asks
var bids = orderBook.Bids; // All bids
var bestBid = orderBook.BestBid; // The best bid available in the book
var bestAsk = orderBook.BestAsk; // The best ask available in the book

The order book will automatically reconnect when the connection is lost and resync if it detects the sequence is off. Make sure to check the Status property to see it the book is currently in sync.

To stop synchronizing an order book use the Stop method.

Release notes

• Version 3.0.1 - 14 Nov 2019

  • Re-enabled debug response logging

• Version 3.0.0 - 23 Oct 2019

  • Updated to C# 8.0
  • Added .NetStandard2.1 support
  • Added Nullability support
  • Now using HttpClient instead of WebRequest, should result in faster consequtive requests
  • Added CancellationToken support
  • Added bool compare override to CallResult (now possible to if(callresult) instead of if(callresult.Success))
  • Added input validation methods
    • Wrong input will now throw exceptions rather than error results
  • OnOrderBookUpdate event added to SymbolOrderBook

• Version 2.1.8 - 29 Aug 2019

  • Added array serialization options for implementations

• Version 2.1.7 - 07 Aug 2019

  • Fixed bug with socket connection not being disposed after lost connection
  • Resubscribing after reconnecting socket now in parallel

• Version 2.1.6 - 06 Aug 2019

  • Fix for missing subscription events if they are also a request response, added code docs

• Version 2.1.5 - 09 jul 2019

  • Updated SymbolOrderBook

• Version 2.1.4 - 24 jun 2019

  • Added checks for json deserialization issues

• Version 2.1.3 - 16 may 2019

  • Refactored SymbolOrderBook
  • Added BestBid/BestAsk properties for order book

• Version 2.1.2 - 14 may 2019

  • Added order book base class for easy implementation
  • Added additional constructor to ApiCredentials to be able to read from file