Skip to main content

HX108 Market Data And Order Flow

HX108 teaches the platform layer behind charts, order-flow tools, provider instruments, and data storage. This is where HyperionX goes beyond basic scripting: users need to understand provider metadata, market depth, imported data, active-chart context, and workspace restore.

Lesson 1: Provider Capabilities​

Every provider must be validated by capability, not by name.

Provider capability areas include:

  • Instrument search and metadata.
  • Historical candles or ticks.
  • Live candles or ticks.
  • Market depth.
  • Account balances.
  • Open orders.
  • Positions.
  • Order submission.
  • Order modification.
  • Cancel and flatten.
  • Leverage or margin support.
  • Fees, multipliers, tick size, and lot size.

Do not teach that every provider supports every area. Provider support can differ by build, credentials, market type, account type, and exchange permissions.

Lesson 2: Instrument Metadata​

Instrument metadata controls order sizing, chart precision, and research accuracy.

Teach users to verify:

  • Symbol.
  • Exchange/venue.
  • Asset type.
  • Base asset.
  • Quote asset.
  • Currency or settlement currency.
  • Tick size or price increment.
  • Minimum lot size.
  • Quantity step.
  • Multiplier.
  • Minimum notional.
  • Max leverage where supported.
  • Provider-specific fields.

If metadata is wrong, then spread, PnL, margin, position size, historical tests, and validator results can all be wrong.

Lesson 3: Connections And Instrument Lists​

Instrument selection should come from connected providers where possible.

Training flow:

  1. Connect the provider.
  2. Open instruments.
  3. Search by symbol, base, quote, category, or provider type.
  4. Confirm metadata before adding to local lists.
  5. Map provider symbols to local instruments when needed.
  6. Use the selected chart context when opening Level 2, DOM, or Time and Sales.

For crypto perps, users should confirm whether the selected instrument is spot, futures, or perpetual before placing orders or running tests.

Lesson 4: Historical Data Storage​

HyperionX stores historical data with metadata. Imported data and downloaded provider data must stay consistent.

Teach:

  • Use Import Historical Data for external files.
  • Label imported external futures data as Historical Data.
  • Preserve metadata for symbol, provider, timeframe, and date range.
  • Warn before overwriting existing symbol/date data.
  • Convert tick data to minute/day bars only through a supported conversion path.
  • Prefer incremental imports and skip existing files when possible.
  • Keep long imports non-blocking where the platform supports background work.

Do not tell users to hand-edit stored data files.

Lesson 5: Market Depth Tools​

Market depth tools are provider-dependent.

HyperionX training should cover:

  • Level 2 window.
  • DOM/SuperDOM style window.
  • Mega DOM or modular trading workspace where available.
  • Bid/ask ladder behavior.
  • Spread calculation.
  • Best bid/best ask.
  • Depth aggregation.
  • Provider timestamp/status text.
  • Refresh/reconnect behavior.

If market depth is unavailable, teach users to check provider capability, connection state, instrument support, and logs before assuming the window is broken.

Lesson 6: Time And Sales​

Time and Sales should open from the active chart context when possible.

Teach:

  • Select the chart first in multi-chart mode.
  • Open Time and Sales from the main toolbar/menu.
  • Confirm the window title shows the instrument.
  • Confirm prints match the selected provider/instrument.
  • Keep separate windows for separate instruments when needed.

This avoids opening order-flow tools for the wrong chart in multi-chart layouts.

Lesson 7: Workspaces And Window Restore​

Workspaces are part of the platform workflow, not just UI convenience.

Workspace restore should be validated for:

  • Main window size and position.
  • Chart windows and chart layouts.
  • Chart instruments and timeframes.
  • Indicator parameters.
  • Chart Trader visibility.
  • Level 2 windows.
  • Time and Sales windows.
  • DOM windows.
  • Validator and Optimizer windows where supported.
  • Window positions and sizes.

Users should make separate workspaces for live trading, research, and development.

Lesson 8: Order-Flow Troubleshooting​

When order-flow tools look wrong, check in this order:

  1. Active chart selection.
  2. Connection state.
  3. Provider market-depth support.
  4. Instrument metadata.
  5. Best bid/best ask.
  6. Spread calculation.
  7. Tick size.
  8. Quantity precision.
  9. Provider timestamp/status message.
  10. Logs.

Completion check:

  • User can explain the difference between chart data, historical data, and market depth.
  • User can verify instrument metadata before trading.
  • User can open Level 2, DOM, and Time and Sales from the active chart context.
  • User can identify when a provider does not support an order-flow feature.
  • User can save and restore a workspace with the relevant windows open.