Menu
TDP has a static JSON data API where race data is retrieved for your server and / or client
Requests via the client must route via your own API’s and not go directly to TDP’s API. Your API key is appended to client request parameters at your server side API level which requests data from us. This data is then transported back to your client. You must not made client calls directly to your client with your API Key.
Full examples are given in the GitHub public repo.
Web sockets are set up via your client directly to TDP’s web socket.
An API request is made (via your server) for a 1 time access key that is linked with your API key, streaming vendor key, the race identifier and the clients IP address.
The socket connection includes this key and is verified and a valid connection request.
Real time data is then pushed over the socket to your client for live racing views, this data includes positional, velocity and performance metrics data about the race requested.
This method is suited to small to medium companies that need a rapid and easy to implement solution.
TPD can supply a UDP feed directly to your server with race progress and / or runner data packets. Your servers then transport this data to your clients in any way you wish to.
This solution is more suited to large companies that wish to have full control over delivery and third party connections.