Sethealth dotnet client allows to access the backend sethealth API from a server. The unique use case of this library today is to provide a authentication schema to delegate the "frontend" javascript library to communicate safely with the sethealth backend.

This is accomplish by the generation of a service account in sethealth. A service account is a long-living account for non-human users, like servers. Once a service account is created, a api key and a api secret are generated, this credentials MUST be kept private, never exposed in a client side application.

This "long-living" credentials can be used instead to create short-living credentials in the shape of access tokens in order to call the upload/download medical data from the client.

The package can be found at the Nuget Gallery

dotnet add package Sethealth.net --version X.X.X

PM> Install-Package Sethealth.net -Version X.X.X

<PackageReference Include="Sethealth.net" Version="X.X.X" />

paket add Sethealth.net --version X.X.X

Get your service account credentials from the Sethealth Dashboard.

.bashrc/.zshrc:*

export SETHEALTH_KEY="sa_0000000000000"
export SETHEALTH_SECRET="xxxxxxxxxxxxxxxxxxxxxxxxxxxxx="

Main.cs:*

using Sethealth;

# Create sethealth client
var client = new Client();

# Ask for a short-living access token
GetTokenResponse response = await client.GetToken();
Console.WriteLine("ACCESS TOKEN {0}", response.token);

Alternatively, the credentials can be provided programatically by passing the api key and the api secret as arguments to Client.

using Sethealth;


# Credentials
var apiKey = "HERE THE API KEY";
var apiSecret = "HERE THE API SECRET";
var client = new Client(apiKey, apiSecret);

# Ask for a short-living access token
GetTokenResponse response = await client.GetToken();
Console.WriteLine("ACCESS TOKEN {0}", response.token);

Note: Credentials should be kept secret, it's not a good practice to hard code them in the source code.

1. Update version in Sethealth.net/Sethealth.net.csproj
2. Run make release