Skip to main content
Market data is the read side of the engine: the symbol catalog, OHLCV history, batch quotes, and two live streams over Server-Sent Events. It is public in shape but licensed in access — served to first-party origins and authenticated callers.

What you can build

  • A chartfind the symbol, read its tick and price format, backfill history, then stream live bars. Four calls, in that order.
  • A scroll-back that knows when to stopcountBack pages backwards from a timestamp, and noData says there is nothing older to ask for.
  • A watchlist — batch quote snapshots for up to 50 symbols in one call, answered in request order, with a symbol that has no feed coming back all-null rather than dropped.
  • A multi-chart layout — one multiplexed connection carries every bar subscription you hold, up to 24.
  • Synthetic instruments — a spread expression over up to four legs, evaluated server-side, that resolves, backfills and streams like any other instrument.
  • Correct prices without hardcoding an exchange — tick size, price format, session model and the served holiday calendar all come off the wire.
  • News and calendar surfaces — aggregated headlines and economic events, each with its own stream.

Core objects

A symbol row, an OHLCV bar, a quote snapshot, and the futures contract catalog. Fetch market-data limits once before your first data call — it answers the questions the other routes assume.

Where to go next

Find symbols

The limits, the catalog, and the tick, format and session a ticket needs.

Backfill history

Windows, countBack paging, and spread expressions.

Stream live data

The snapshot-then-events contract that heals its own reconnects.

Bring data via your venue

Why a trader’s own venue login is what serves their charts.

Publish a datafeed

Serving a market the engine does not connect to.

Streaming

The reconnect contract in full.