Tardis Machine Server
Locally runnable server with built-in data caching, providing both tick-level historical and consolidated real-time cryptocurrency market data via HTTP and WebSocket APIs
Last updated
Locally runnable server with built-in data caching, providing both tick-level historical and consolidated real-time cryptocurrency market data via HTTP and WebSocket APIs
Last updated
is a locally runnable server with built-in data caching that uses Tardis.dev under the hood. It provides both tick-level historical and consolidated real-time cryptocurrency market data via it's HTTP and WebSocket APIs and is available via and .
consistent format for accessing market data across multiple exchanges
transparent historical local data caching (cached data is stored on disk in compressed GZIP format and decompressed on demand when reading the data)
Tardis-machine server's HTTP endpoints will be available on port 8000
and WebSocket API endpoints on port 8001
. Your API key will be passed via ENV variable (TM_API_KEY
) — simply replace YOUR_API_KEY
with API key you've received via email.
Since using volumes can cause issues especially on Windows, it's fine to run Docker image without them with the caveat of potentially poor local cache ratio after each container's restart.
You can set following environment config variables to configure tardis-machine server:
name
default
description
TM_API_KEY
TM_PORT
8000
HTTP port on which server will be running, WebSocket port is always this value + 1 (8001
with port set to 8000
)
TM_CACHE_DIR
/.cache
path to local dir that will be used as cache location
TM_CLUSTER_MODE
false
TM_DEBUG
false
server will print verbose debug logs to stdout if set to true
TM_CLEAR_CACHE
false
server will clear local cache dir on startup if set to true
Install and runtardis-machine
server via npx
command:
or install globally via npm
:
and then run:
Tardis-machine server's HTTP endpoints will be available on port 8000
and WebSocket API endpoints on port 8001
. Your API key will be passed via --api-key
config flag — simply replace YOUR_API_KEY
with API key you've received via email.
You can set following CLI config flags when starting tardis-machine server installed via npm
:
name
default
description
--api-key
--port
8000
HTTP port on which server will be running, WebSocket port is always this value + 1 (8001
with port set to 8000
)
--cache-dir
<os.tmpdir>/.tardis-cache
path to local dir that will be used as cache location - if not provided default temp
dir for given OS will be used
--cluster-mode
false
--debug
false
server will print verbose debug logs to stdout if set to true
--clear-cache
false
server will clear local cache dir on startup is set to true
--help
shows CLI help
--version
shows tardis-machine version number
HTTP GET
/replay?options={options}name
type
default
exchange
string
-
filters
{channel:string, symbols?: string[]}[]
[]
from
string
-
to
string
-
withDisconnects
boolean | undefined
undefined
when set to true
, response includes empty lines (\n
) that mark events when real-time WebSocket connection that was used to collect the historical data got disconnected
localTimestamp
- date when message has been received in ISO 8601 format
message
- JSON with exactly the same format as provided by requested exchange real-time feeds
Sample response
WebSocket
/ws-replay?exchange={exchange}&from={fromDate}&to={toDate}After connection is established, client has 2 seconds to send subscriptions payloads and then market data replay starts.
name
type
default
description
exchange
string
-
from
string
-
to
string
-
session
string | undefined
undefined
optional replay session key. When specified and multiple clients use it when connecting at the same time then data being send to those clients is synchronized (by local timestamp).
HTTP GET
/replay-normalized?options={options}Options JSON needs to be an object or an array of objects with fields as specified below. If array is provided, then data requested for multiple exchanges is returned synchronized (by local timestamp).
name
type
default
exchange
string
-
symbols
string[] | undefined
undefined
from
string
-
to
string
-
dataTypes
string[]
-
withDisconnectMessages
boolean | undefined
undefined
WebSocket
/ws-replay-normalized?options={options}Options JSON needs to be an object or an array of objects with fields as specified below. If array is provided, then data requested for multiple exchanges is being send synchronized (by local timestamp).
name
type
default
exchange
string
-
symbols
string[] | undefined
undefined
from
string
-
to
string
-
dataTypes
string[]
-
withDisconnectMessages
boolean | undefined
undefined
WebSocket
/ws-stream-normalized?options={options}Doesn't requires API key as connects directly to exchanges real-time WebSocket APIs and transparently restarts closed, broken or stale connections (open connections without data being send for specified amount of time).
Options JSON needs to be an object or an array of objects with fields as specified below. If array is specified then API provides single consolidated real-time data stream for all exchanges specified (as in examples above).
name
type
default
exchange
string
-
symbols
string[] | undefined
undefined
optional symbols of requested real-time data feed
dataTypes
string[]
-
withDisconnectMessages
boolean | undefined
undefined
timeoutIntervalMS
number
10000
specifies time in milliseconds after which connection to real-time exchanges' WebSocket API is restarted if no message has been received
Individual trade
Derivative instrument ticker info sourced from real-time ticker & instrument channels.
book_snapshot_10_0ms
- provides top 10 levels tick-by-tick order book snapshots
book_snapshot_50_100ms
- provides top 50 levels order book snapshots taken at 100 millisecond intervals
book_snapshot_30_10s
- provides top 30 levels order book snapshots taken at 10 second intervals
quote
is an alias of book_snapshot_1_0ms
- provides top of the book (best bid/ask) tick-by-order book snapshots
quote_10s
is an alias of book_snapshot_1_10s
- provides top of the book (best bid/ask) order book snapshots taken at 10 seconds intervals
ms
- milliseconds
s
- seconds
m
- minutes
Trades data in aggregated form, known as OHLC, candlesticks, klines etc. Not only most common time based aggregation is supported, but volume and tick count based as well. Bars are computed from tick-by-tick raw trade data, if in given interval no trades happened, there is no bar produced.
trade_bar_10ms
- provides time based trade bars with 10 milliseconds intervals
trade_bar_5m
- provides time based trade bars with 5 minute intervals
trade_bar_100ticks
- provides ticks based trade bars with 100 ticks (individual trades) intervals
trade_bar_100000vol
- provides volume based trade bars with 100 000 volume intervals
Allowed suffixes:
ms
- milliseconds
s
- seconds
m
- minutes
ticks
- number of ticks
vol
- volume size
Message that marks events when real-time WebSocket connection that was used to collect the historical data got disconnected.
efficient data replay API endpoints returning historical market data for whole time periods (in contrast to Tardis.dev where single call returns data for single minute time period)
tick-by-tick historical market data replay in
and endpoints
providing historical market data replay from any given past point in time with the same data format and 'subscribe' logic as real-time exchanges' APIs - in many cases existing exchanges' WebSocket clients can be used to connect to this endpoint
and endpoints
synchronized
connecting directly to exchanges' WebSocket APIs
customizable and data types
seamless
support for top cryptocurrency exchanges: , , , , , , , , , , , , , , , , , and more
Pull and run latest version of :
Command above does not use persistent volumes for local caching (each docker restart will result in loosing local data cache). In order to use for example./host-cache-dir
as persistent volume () cache directory, run:
API key for HTTP API - if not provided only first day of each month of historical data is accessible
will launch to handle the incoming requests if set to true
, by default server runs in single process mode
You can configure tardis-machine server via as described in Docker section as well.
API key for HTTP API - if not provided only first day of each month of historical data is accessible
will launch to handle the incoming requests if set to true
, by default server runs in single process mode
Exchange-native market data API endpoints provide historical data in . The main difference between HTTP and WebSocket endpoints is the logic of requesting data:
accepts payload via query string param
accepts exchanges' specific 'subscribe' messages that define what data will be then "replayed" and send to WebSocket client
Returns historical market data messages in for given replay options query string param. Single streaming HTTP response returns data for the whole requested time period as .
In our preliminary benchmarks on AMD Ryzen 7 3700X, 64GB RAM, API endpoint was returning ~700 000 messages/s (already locally cached data).
See also official Tardis.dev library.
See also official Tardis.dev library.
We're working on providing more samples and dedicated client libraries in different languages, but in the meanwhile to consume API responses in your language of choice, you should:
Provide url encoded JSON via options query string param when sending HTTP request
Parse each response line as JSON containing messages in
endpoint accepts required options query string param in url encoded JSON format.
requested exchange id - use to get list of valid exchanges ids
optional filters of requested historical data feed - check for each exchange and to get allowed channels and symbols for requested exchange
replay period start date (UTC) in a format, e.g., 2019-04-01
replay period end date (UTC) in a format, e.g., 2019-04-02
Streamed HTTP response provides data in NDJSON format (new line delimited JSON) - each response line is a JSON with market data message in plus local timestamp:
Exchanges' WebSocket APIs are designed to publish real-time market data feeds, not historical ones. Tardis-machine API fills that gap and allows "replaying" historical market data from any given past point in time with the same data format and 'subscribe' logic as real-time exchanges' APIs. In many cases existing exchanges' WebSocket clients can be used to connect to this endpoint just by changing URL, and receive historical market data in format for date ranges specified in URL query string params.
If two clients connect at the same time requesting data for different exchanges and provide the same , then data being send to those clients will be synchronized (by local timestamp).
In our preliminary benchmarks on AMD Ryzen 7 3700X, 64GB RAM,
API endpoint was sending ~500 000 messages/s (already locally cached data).
You can also use existing WebSocket client, just by changing URL endpoint as shown in the example below that uses
As long as you already use existing WebSocket client that connects to and consumes real-time exchange market data feed, in most cases you can use it to connect to API as well just by changing URL endpoint.
requested exchange id - use to get list of valid exchanges ids
replay period start date (UTC) in a format, e.g., 2019-04-01
replay period end date (UTC) in a format, e.g., 2019-04-02
Normalized market data API endpoints provide data in across all supported exchanges. Both and APIs accept the same replay options payload via query string param. It's mostly matter of preference when choosing which protocol to use, but has also it's real-time counterpart , which connects directly to exchanges' real-time WebSocket APIs. This opens the possibility of seamless switching between real-time streaming and historical normalized market data replay.
Returns historical market data for specified via query string. Single streaming HTTP response returns data for the whole requested time period as . See which include normalized , , etc.
In our preliminary benchmarks on AMD Ryzen 7 3700X, 64GB RAM, API endpoint was returning ~100 000 messages/s and ~50 000 messages/s when order book snapshots were also requested.
See also official Tardis.dev library.
We're working on providing more samples and dedicated client libraries in different languages, but in the meanwhile to consume API responses in your language of choice, you should:
Provide url encoded JSON via options query string param when sending HTTP request
Parse each response line as JSON containing .
endpoint accepts required options query string param in url encoded JSON format.
requested exchange id - use to get list of valid exchanges ids
optional symbols of requested historical data feed - use to get allowed symbols for requested exchange
replay period start date (UTC) in a format, e.g., 2019-04-01
replay period end date (UTC) in a format, e.g., 2019-04-02
array of normalized for which historical data will be returned
when set to true
, response includes messages that mark events when real-time WebSocket connection that was used to collect the historical data got disconnected
See .
Sends historical market data for specified via query string. See which include normalized , , etc.
is the real-time counterpart of this API endpoint, providing real-time market data in the same format, but not requiring API key as connects directly to exchanges' real-time WebSocket APIs.
See also official Tardis.dev library.
We're working on providing more samples and dedicated client libraries in different languages, but in the meanwhile to consume API responses in your language of choice, you should:
Provide url encoded JSON via options query string param when connecting to
endpoint
Parse each received WebSocket message as JSON containing .
endpoint accepts required options query string param in url encoded JSON format.
requested exchange id - use to get list of valid exchanges ids
optional symbols of requested historical data feed - use to get allowed symbols for requested exchange
replay period start date (UTC) in a format, e.g., 2019-04-01
replay period end date (UTC) in a format, e.g., 2019-04-02
array of normalized for which historical data will be provided
when set to true
, sends also messages that mark events when real-time WebSocket connection that was used to collect the historical data got disconnected
In our preliminary benchmarks on AMD Ryzen 7 3700X, 64GB RAM, API endpoint was returning ~70 000 messages/s and ~40 000 messages/s when order book snapshots were also requested.
See .
Sends real-time market data for specified via query string. See which include normalized , , etc.
Provides consolidated real-time market data streaming functionality with as an array - provides single consolidated real-time data stream for all exchanges specified in .
is the historical counterpart of this API endpoint, providing historical market data in the same format.
See also official Tardis.dev library.
We're working on providing more samples and dedicated client libraries in different languages, but in the meanwhile to consume API responses in your language of choice, you should:
Provide url encoded JSON via options query string param when connecting to
endpoint
Parse each received WebSocket message as JSON containing .
endpoint accepts required options query string param in url encoded JSON format.
requested exchange id - use to get list of valid exchanges ids
array of normalized for which real-time data will be provided
when set to true
, sends messages anytime underlying exchange real-time WebSocket connection(s) gets disconnected
See .
Initial order book snapshot (isSnapshot=true
) plus incremental updates for each order book change. Please note that amount
is the updated amount at that price level, not a delta. An amount
of 0
indicates the price level can be removed.
Order book snapshot for selected number_of_levels
(top bids and asks), snapshot_interval
and .
When snapshot_interval
is set to 0
, snapshots are taken anytime order book state within specified levels has changed, otherwise snapshots are taken anytime snapshot_interval
time has passed and there was an order book state change within specified levels. Order book snapshots are computed from exchanges' real-time order book streaming .