Tick Charts
Request and process tick-level chart data over the WebSocket protocol.
Tick charts use the same process as the Market Data API: open and authorize a WebSocket first, then request chart data. The difference is in the chart description.
If you’re following the JavaScript tutorial, see the tick chart examples.
Requesting Tick Charts
Build a request body with the symbol, chartDescription, and timeRange fields, as you would for any chart. For tick data, lock elementSize to 1 and set underlyingType to "Tick":
Then call the standard md/getChart endpoint with this request. The server responds with the standard chart-data schema. Because unsubscribing requires the real-time subscription ID returned with the response, store the ID of each subscription you create so you can unsubscribe later.
Data Stream Messages
A tick data stream message has the following structure. Tick prices and timestamps are stored relative to each packet’s base values, so you reconstruct actual values by adding the tick’s relative value to the packet’s base:
Processing the Tick Stream
The following snippet converts a data stream message’s packets into a list of actual ticks for consumption. Because tick stream data can arrive out of chronological order, it’s the client’s responsibility to store and sort the relevant portions of this data.

