Creating the application framework

Instead of username and password, applications written with TT .NET SDK must provide an application key / secret pair for authentication. An application key / secret pair is a proxy for a user. TT .NET SDK uses different application keys for client-mode and server-mode applications:

TT .NET SDK application keys are created in the TT Setup application. For more information, see Creating and managing application keys.

Creating a client-side application key/secret pair

Using TT .NET SDK Client Side mode requires you to select a usage plan for the application key that can incur additional costs. For more information about the costs associated with these usage plans, contact TT Customer Success.

Users can create an application key / secret pair from within Setup in the TT Platform as follows:

Creating a server-side application key/secret pair

Using TT .NET SDK requires you to select a usage plan for the application key that can incur additional costs. For more information about the costs associated with the usage plans, contact TT Customer Success.

Users can create an application key / secret pair from within Setup in the TT Platform as follows:

Introduction to Proxy Credentials

To support requesting data from external sources via the internet, some proxy servers may require specific credentials for access. To support this configuration, the TT .NET SDK requires access to the user’s proxy credentials to make the required requests.

Note: In order to connect to a proxy server that requires credentials, you must configure a ProxyCredentialsHandler when creating your application.

Configuring the ProxyCredentialsHandler

When connecting to a proxy server that requires credentials, the TT .NET SDK requests the credentials from the application via the ProxyCredentialsHandler. The credentials provided by the application will be handed to the proxy which, if valid, should allow the TT .NET SDK to access the external internet resources.

The ProxyCredentialsHandler defined in the TTAPI object provides the mechanism to pass proxy credentials to the SDK. When creating your application, configure the handler and pass it into the CreateTTAPI method.

Note: This is an optional handler and may be omitted if the application does not need to support proxies that require credentials.

ProxyCredentialsHandler example

The following code snippet demonstrates an example of this process.

Overriding the system configured proxy

You can override the system configured proxy by setting the TTAPI.ProxyUri property equal to the Uniform Resource Identifier of your desired proxy server.

To develop and execute TT .NET SDK applications, you need to be authorized by your company administrator in TT Setup. Additionally, you will need to create an app key to authenticate your application.

To create a Console application, you need to:

Client-side mode example

The following code snippet demonstrates an example of this process for client-side mode.

Server-side mode example

The following code snippet demonstrates an example of this process for server-side mode.

To create a UI application, you need to:

Client-side mode example

The following code snippet demonstrates an example of this process for client-side mode.

Server-side mode example

The following code snippet demonstrates an example of this process for server-side mode.

The TT .NET SDK Diagnostic Tool helps you troubleshoot problems that might arise when trying to authenticate a TT .NET SDK application. If you get an authentication error in your ApiInitializeHandler callback, you can use the tool to help determine why your app key is not valid for the application.

Some common issues with application keys include:

The TT .NET SDK Diagnostic Tool is included in the NuGet software library package and is installed in the location associated with your application’s Visual Studio solution.

To use the TT .NET SDK Diagnostic Tool:

TT .NET SDK is inherently multi-threaded, using events to notify TT .NET SDK applications of new data, such as order status changes, price updates, or fill notifications. Because your applications can use multiple threads to access TT .NET SDK functionality, each thread that interacts with TT .NET SDK must have an attached Dispatcher object that routes events and data across threads.

TT .NET SDK supports the following Dispatcher types:

Note: .NET 5 does not support a UIDispatcher.

Note that both the UIDispatcher and WorkerDispatcher classes derive from the UIDispatcher class. You can always access your current Dispatcher object in any TT .NET SDK thread by calling Dispatcher.Current.

Dispatcher Suggestions

The UIDispatcher is only supported on Windows Operating Systems. To support multiple platforms, the .NET 5 version of the TT .NET SDK does not support the UIDispatcher.

TT recommends writing a dispatcher to push messages to the UI thread for the specific operating system that will run the application.

For Windows users, TT suggests users look into System.Windows.Threading.Dispatcher to push messages to the UI.