BTC, while each event retains its exact contract
identifier.
Representative coverage
This snapshot comes from the public Catalog at2026-08-29T15:40:40.625Z. Coverage changes as datasets are added or updated,
so use Catalog before building a request.
Preview access can change by date and account. Read the selected catalog row’s
start, end, and access fields before choosing a time range.
Understand option identity
Options use three identifiers:
Pass the underlying as
market. Omit instrument to read the whole chain, or
pass an exact returned value to isolate one contract. Do not derive a contract
ID from another venue’s naming convention.
Choose a client method
Use
option_tickers when you need typed ticker fields such as prices, implied
volatility, open interest, or Greeks. Use events or replay when ticker events
must remain interleaved with other event types. Use raw only when you need
venue-specific fields that are absent from the standardized event.
See Python SDK, TypeScript SDK, and
Rust SDK for complete signatures and return behavior.
Build a current chain snapshot
Option ticker events are partial updates. A missing field means the venue did not publish it in that event; it does not mean zero. Build a snapshot by sorting updates, carrying the last published value forward per instrument, and then retaining the latest row for each contract. Install the DataFrame extra first:Monitor a contract
After you discover an exactinstrument, use the same identity for historical
and realtime filtering:
Related documentation
- Option tickers for parameters, event fields, units, and multi-language examples
- Event envelope for timestamps and stored ordering
- Catalog for current source, market, and access metadata
- Events for mixed standardized event streams