Contract Prices
/timeseries/market-contract-prices
Last updated
Was this helpful?
/timeseries/market-contract-prices
Last updated
Was this helpful?
Market contract prices are prices relevant to derivatives contract. It consists of the mark price, index price, and estimated settlement price.
The estimated settlement price is an estimate of the settlement price if the contract were to be settled
Exchanges report the following contract prices:
Mark price: The mark price is used by an exchange to calculate a trader's unrealized profit and losses and to trigger liquidations for risk management purposes. Each exchange applies a unique methodology for calculating the mark price, which typically is a function of the index price, funding rate, and the best bid and best ask with some smoothing applied over a time interval to address market manipulation or volatility. This prevents unnecessary liquidations during volatile market environments. Exchanges typically do not use the last traded price for risk management purposes because it is susceptible to market manipulation.
Index price: The price of the derivative contract's underlying index. Each exchange applies a unique methodology for calculating the index price, which typically involves weighting the prices from spot markets from multiple different exchanges.
Estimated settlement price: An estimate of the settlement price if the contract were to be immediately settleed. Each exchange applies a unique methodology for calculating the final settlement price, which typically involves an average of the index price over some interval. The estimated settlement price applies this methodology continuously in real-time. The estimated settlement price can be helpful in hedging or calculating estimated profit and loss prior to contract expiration.
Market contract prices can be accessed using the timeseries/market-contract-prices endpoint.
A sample of contract price data from our /timeseries/market-contract-prices API endpoint is shown below for the deribit-ETH-25MAR22-1200-P-option market.
market: The id of the market. Market ids use the following naming convention for options markets: exchangeName-optionsSymbol-option
time: The time at which Coin Metrics queried the contract price from an exchange in ISO 8601 date-time format. Always with nanoseconds precision.
mark_price: The instrument market price, which represents the contract's fair market value and is used to calculate a trader's unrealized profit and losses and to trigger liquidations for risk management purposes.
index_price: The price of the underlying benchmark index.
settlement_price_estimated: Represents what the underlying index settlement price would be if the contract immediately expired.
database_time: The timestamp when the data was saved in the database in ISO 8601 date-time format with nanoseconds precision. Always with nanoseconds precision.
exchange_time: The timestamp reported by the exchange. Can be null if the exchange does not report a timestamp.
CM MDF v2.5 on November 22, 2021: We expanded our options coverage to include several new data types, including market contract prices, from Deribit and added several new API endpoints to serve this data.
CM MDF v2.7 on October 24, 2022: Began collecting and serving the settlement price and estimated settlement price for option markets. The settlement price is served in our /catalog/markets endpoint and is available shortly after an option market expires. And the estimated settlement price is updated once a minute and served in our /timeseries/market-contract-prices endpoint.
Returns contract prices for specified markets. This includes index price and mark price that are used by the exchange for settlement and risk management purposes.<br/> Results are ordered by tuple (market, time).<br/> To fetch the next page of results use next_page_url JSON response field.<br/>
/timeseries/market-contract-prices
Comma separated list of markets or market patterns like exchange-* or exchange-*-spot or *USDT-future.<br/> Use the /catalog-all/markets endpoint for the full list of supported markets.
Start of the time interval.<br/> This field refers to the time field in the response.<br/> Multiple formats of ISO 8601 are supported: 2006-01-20T00:00:00Z, 2006-01-20T00:00:00.000Z, 2006-01-20T00:00:00.123456Z, 2006-01-20T00:00:00.123456789Z, 2006-01-20, 20060120.<br/> Inclusive by default.<br/> UTC timezone by default. Z suffix is optional and timezone parameter has a priority over it.<br/> If start_time is omitted, response will include time series from the earliest time available.
End of the time interval.<br/> This field refers to the time field in the response.<br/> Multiple formats of ISO 8601 are supported: 2006-01-20T00:00:00Z, 2006-01-20T00:00:00.000Z, 2006-01-20T00:00:00.123456Z, 2006-01-20T00:00:00.123456789Z, 2006-01-20, 20060120.<br/> Inclusive by default.<br/> UTC timezone by default. Z suffix is optional and timezone parameter has a priority over it.<br/> If end_time is omitted, response will include time series up to the latest time available.
Inclusive or exclusive corresponding start_* parameters.
Inclusive or exclusive corresponding end_* parameters.
Downsampling granularity of market contract prices. Supported values are raw, 1m, 1h, and 1d.
raw, 1m, 1h, 1dTimezone name for start_time and end_time timestamps.<br/> This parameter does not modify the output times, which are always UTC.<br/> Format is defined by TZ database.
America/New_YorkNumber of items per single page of results.<br/> The value of this parameter is ignored if the endpoint supports the format parameter and its value is set to json_stream.
Where does the first page start, at the start of the interval or at the end.
start, endHow many entries per market result should contain. It is useful when multiple markets are requested.
Human-readable formatting of JSON responses.
Format of the response.
json, csvToken for receiving the results from the next page of a query.<br/> Should not be used directly. To iterate through pages just use next_page_url response field.