TT^® REST API 2.0

Introduction to TT REST API

The TT REST API 2.0 gives you the tools you need to leverage the power of the TT platform within your own applications. You can access the same product information services, risk management and market connectivity used by the TT platform - all through an easy-to-use REST API.

The TT REST API provide a number of resources:

ttid: Authenticate and authorize applications to access the resources of the TT platform.
ttpds: Request information pertaining to exchanges, products and instruments.
ttledger: View transaction details and historical record.
ttmonitor: Add administrative fills and view credit limits, credit utilitzation, position, and Start-of-Day (SOD) records for a given account.
ttsetup: View and set company-level product margins, order tag defaults, exchange connections, and organizations.
ttuser: View and set risk limits, market data access, contracts, and product settings for given users or user groups.
ttaccount: View and set risk limits, trade permissions, and users for a given account.
ttgroup: Create and manage risk limits for risk groups, risk accounts, and user groups.

Note: When submitting requests, all API urls are case sensitive and should include the endpoint name in lowercase. For example, using https://ttrestapi.trade.tt/TTUser/ext_uat_cert/ results in a 403 server error.

You must use https://ttrestapi.trade.tt/ttuser/ext_uat_cert/ in order to properly reach the API.

To view a sample application which makes use of the TT REST API, visit TT's public Github repository.

Note: The ttledger and ttmonitor services are not intended to be used as a real-time feed since there may be delays between the time at which order and fill events occur and the time when they are available via TT REST API. Applications requiring a real-time feed should use TT .NET SDK or TT FIX.

Environments: directing your requests

TT provides two environments for use with the TT REST API, a UAT environment which is used when developing and testing your application, and a production environment. Requests to the TT REST API target the environment and requested service use the following base URL:

ttrestapi.trade.tt/<service>/<environment>.

The value for <service> is documented on each service's page.
The testing environment can be reached by using the following value: ext_uat_cert
The production environment used when deploying your application can be reached by using: ext_prod_live

Note: To ensure proper routing of all requests, users must use an HTTP library that supports 303 redirects.

Certificate/SSL Validation

Certificate pinning, sometimes known as SSL pinning, is a process that you can use in your application to validate a remote host by associating that host directly with its X.509 certificate or public key instead of with a certificate hierarchy. The application therefore uses pinning to bypass SSL/TLS certificate chain validation.

The typical SSL validation process checks signatures throughout the certificate chain from the root certificate authority (CA) certificate through the subordinate CA certificates, if any. It also checks the certificate for the remote host at the bottom of the hierarchy. Your application can instead pin to the certificate for the remote host to say that only that certificate and not the root certificate or any other in the chain is trusted.

You can add the remote host's certificate or public key to your application during development. Alternatively, the application can add the certificate or key when it first connects to the host.

Warning TT does not support certificate pinning for this service.

Staying Current with TT REST API Releases

It is important to stay current on all of the latest changes that TT makes in the TT REST API. You can subscribe for automated email notifications when new versions of the TT REST API are released by clicking the 'Subscribe' button on the TT Release Notes web page. Although we strive to keep the interface completely backwards compatible in new versions, there may be instances where this is not possible and, as such, will require developers to recompile and/or make code changes.

Contacting TT Support