TT API is our API for the X_TRADER platform that enables developers to design both server-based trading algorithms for proximity-based deployment as well as client-based graphical applications to augment the functionality of X_TRADER. It provides a normalized Microsoft .NET interface for instruments, market data, and order routing for the world’s leading derivatives markets.
To address the needs of traders on the TT platform, we are developing a few new APIs that will be rolled out in succession this year. Each of these will target distinct use cases for which TT API is currently being utilized.
TT .NET SDK (client side)
The first of these APIs is TT .NET SDK (client side), which allows developers to create client side applications that can be run on their own hardware, whether it be in a co-location facility or on a desktop. These applications run outside the TT ecosystem and connect to a TT Edge Server for instruments, coalesced market data (15 milliseconds for inside market / 60 milliseconds for depth), and order routing. And in terms of performance, the latency of an order routing message from the time at which it enters the TT Edge Server to the time that it exits TT bound for the exchange is on the order of several hundred microseconds.
The TT .NET SDK (client side) interface has been designed to mirror that of the TT API as closely as possible to minimize the work required to migrate existing applications. However, some changes will be required since the new TT platform is fundamentally different. For example, quantities in 7x TT API are represented as an integer. However, quantities in the new TT platform are represented as a decimal to accommodate the fact that crypto-currency exchanges have a minimum tradable amount of less than one.
TT .NET SDK (client side) is currently nearing the end of a Developer Preview phase. This means that the interface is solid and we’ll be moving to a beta phase shortly. Customers are welcome to begin their development as well as run their applications in any TT environment.
Documentation is located here. It includes links to download the software and sample code. It also includes a Migration Guide with information for customers who need to migrate their 7x TT API applications. Prior to beginning, developers should ensure that they have access to the User Acceptance Testing (UAT) environment. Access to the UAT environment can be obtained by contacting Sales or Customer Success. Developers can open support tickets for any issues that they encounter. They can also post to the TT Community Forums.
TT .NET SDK (server side)
The second of the new APIs is TT .NET SDK (server side), which will allow developers to create latency sensitive applications that they will run inside the TT ecosystem on a dedicated Windows server in a co-location facility designated by them. It will use the same .NET interface as TT .NET SDK (client side) allowing you to develop applications independent of where they will be deployed, much like TT API.
TT Core SDK
The third of the new APIs is TT Core SDK, which is similar to TT .NET SDK (server side) except that it is a C++ / Linux API. In other words, it will allow developers to create latency sensitive applications that they can run inside the TT ecosystem on a dedicated Linux server in a co-location facility designated by them.
Server-side Performance
Both TT .NET SDK (server side) and TT Core SDK will deliver uncoalesced market data. And in terms of performance, the latency of an order routing message from the time at which it is sent by the customer’s application to the time that it exits TT bound for the exchange is anticipated to be on the order of dozens of microseconds, although TT Core SDK will be slightly faster. Subsequent “Prime” configurations will bring these numbers down even lower. In all cases, these latency numbers are vastly superior to those of TT API on the X_TRADER platform.
Roadmap
While TT .NET SDK (client side) is nearing beta, TT .NET SDK (server side) and TT Core SDK are currently in development. We are targeting to enter a Developer Preview phase for TT .NET SDK (server side) mid-year. More information will be forthcoming as we make further progress.
Contributors
22 People are following this .
