Skip to main content

Reference data

Combination Orders: Combination orders are treated as orders on outright books and are not differentiated in any way. Their orderbook_id links to a combination order book.
Multicast is the recommended source for full reference data. The Starbase REST API exposes a subset of instrument fields and does not include all attributes available in the SBE InstrumentDefinition message — for example, minOrderQuantity is not available via REST. Use the multicast reference data feed to obtain complete instrument definitions.

Reference data sources

The Starbase and standard Deribit APIs expose overlapping, but not identical, instrument metadata: Do not assume that a field available through one interface is available through every other interface. In particular, use the multicast InstrumentDefinition when constructing or validating SBE order-entry messages.

Index prices and derived statistics

Index prices, mark prices, price bands, funding, and open interest are published on the multicast feeds via three dedicated messages: On the snapshot channel, every cycle starts with IndexInfo messages — one for each known index price on the channel, batched into as few packets as fit — so snapshot joiners receive current index prices before the per-instrument sequences. These values are also available from the standard Deribit API:

Quantity units and contract size

Starbase does not use contract counts or contract size for matching. All SBE order, quote, trade, and position quantities use Deribit’s native amount: Encode amounts directly as Decimal72, determine whether the amount represents dollar value or coins from quantityAsset, and validate the value against minOrderQuantity.
Do not derive a contract count before sending an SBE quantity, and do not copy a FIX OrderQty expressed in contracts into an SBE message. contract_size and FIX ContractMultiplier remain available for standard JSON-RPC and FIX workflows, but Starbase does not consume either value.
Starbase is designed as a closed system for latency-sensitive matching. Broker, clearing, and other account-management workflows remain on the standard Deribit APIs, so applications that use those workflows may still need the standard reference data in addition to the Starbase feed.

InstrumentDefinition (10)

The table below outlines the content of field 13 (flags) of InstrumentDefinition.
quantityExponent (field 11) is available via the multicast snapshot only — it is not present in get_instruments on any API. It derives from the instrument’s quantity tick size: a tick of 1 maps to 0, 0.1 to -1, 0.01 to -2, and so on.

IndexInfo (12)

Sent when an index price changes, and at the start of every snapshot cycle (one per known index price on the channel, batched into as few packets as fit). The index price is per currency pair and is shared across the pair’s instruments.

InstrumentInfo (14)

Frequently updated per-instrument fields.

InstrumentRef (15)

Less frequently updated per-instrument fields. All value fields are optional — a field carries its null value when not applicable to the instrument (for example, funding fields on dated futures).

InstrumentStatusUpdate (16)