.NET client for Nakama server written in C#.
Switch branches/tags
Clone or download


Nakama .NET

.NET client for Nakama server written in C#.

Nakama is an open-source server designed to power modern games and apps. Features include user accounts, chat, social, matchmaker, realtime multiplayer, and much more.

This client implements the full API and socket options with the server. It's written in C# with minimal dependencies to support Unity, Xamarin, Godot, XNA, and other engines and frameworks.

Full documentation is online - https://heroiclabs.com/docs

Getting Started

You'll need to setup the server and database before you can connect with the client. The simplest way is to use Docker but have a look at the server documentation for other options.

  1. Install and run the servers. Follow these instructions.

  2. Download the client from the releases page and import it into your project. You can also build from source.

  3. Use the connection credentials to build a client object.

    // using Nakama;
    var client = new Client("defaultkey", "", 7350, false)
        Timeout = 10000, // set timeout on requests (default is 5000).
        Retries = 5      // set retries on requests (default is 3).


The client object has many methods to execute various features in the server or open realtime socket connections with the server.


There's a variety of ways to authenticate with the server. Authentication can create a user if they don't already exist with those credentials. It's also easy to authenticate with a social profile from Google Play Games, Facebook, Game Center, etc.

var email = "super@heroes.com";
var password = "batsignal";
var session = await client.AuthenticateEmailAsync(email, password);


When authenticated the server responds with an auth token (JWT) which contains useful properties and gets deserialized into a Session object.

System.Console.WriteLine(session.AuthToken); // raw JWT token
System.Console.WriteLine("Session has expired: {0}", session.IsExpired);
System.Console.WriteLine("Session expires at: {0}", session.ExpireTime);

It is recommended to store the auth token from the session and check at startup if it has expired. If the token has expired you must reauthenticate. The expiry time of the token can be changed as a setting in the server.

var authtoken = "restored from somewhere";
var session = Session.Restore(authtoken);
if (session.IsExpired)
    System.Console.WriteLine("Session has expired. Must reauthenticate!");


The client includes lots of builtin APIs for various features of the game server. These can be accessed with the async methods. It can also call custom logic as RPC functions on the server. These can also be executed with a socket object.

All requests are sent with a session object which authorizes the client.

var account = await client.GetAccountAsync(session);


The client can create one or more sockets with the server. Each socket can have it's own event listeners registered for responses received from the server.

var reconnects = 5; // set reconnect attempts (default is 3).
var socket = client.CreateWebSocket(reconnects);
socket.OnConnect += (sender, args) =>
    System.Console.WriteLine("Socket connected.");
await socket.ConnectAsync(session);


The development roadmap is managed as GitHub issues and pull requests are welcome. If you're interested to enhance the code please open an issue to discuss the changes or drop in and discuss it in the community chat.

Source Builds

The codebase can be built with Cake. All dependencies are downloaded at build time with Nuget.

./build.sh --target=Build

With Windows use the PowerShell script instead.

.\build.ps1 --target=Build

Run Tests

To run tests you will need to run the server and database. Most tests are written as integration tests which execute against the server. A quick approach we use with our test workflow is to use the Docker compose file described in the documentation.

docker-compose -f ./docker-compose.yml up
./build.sh --target=Run-Unit-Tests


This project is licensed under the Apache-2 License.

Special Thanks

Thanks to Alex Parker (@zanders3) for the excellent json library.