Markets Open Interest History

查询 Crypto 未平仓量(OI)历史序列。

GET/api/v1/markets/open-interest-history
Domain
Market & Liquidity
Level
asset-level
MCP tool
market_data_query (task=open_interest_history)

Available data

Query level: asset-level.

  • Input must resolve to one asset (ticker / name).
  • Name multi-match → HTTP 200 with resolution_status=ambiguous and data[] candidates (no silent binding).
  • Resolution priority: object IDs > ticker/name; a bare ticker requires market or venue_id.
  • context.market is for fuzzy disambiguation only — it never overrides an exact ticker or listing_id.

Authentication

Send Authorization: Bearer YOUR_API_KEY or X-API-KEY on every request.

Query Parameters

asset_idstringqueryExampleasset_btcrequired

Catalog asset ID (e.g. asset_btc) or symbol (e.g. BTC).

limitintegerqueryExample20optional

Max rows to return (up to 1000).

Response

metadataobject

Response status and resolution information

data_statusDataStatusExamplenot_ready

ready / ok / partial / no_data / not_ready (surface-specific)

limitations[]string[]Exampledata_not_ready

Known data limitations

updated_atdatetime | string

Most recent object or response update time

partialboolean

Whether the response contains only a subset of fields

resolution_reasonstring

Reason code for the object-resolution outcome

object_refs[]object[]

Unified object references

Object reference type

idstring

Canonical object identifier

entity_idstring

Canonical entity identifier

asset_idstring

Canonical asset identifier

listing_idstring

Canonical listing identifier

instrument_idstring

Canonical financial instrument identifier

venue_idstring

Canonical trading venue identifier

event_refstring

Related event identifier

market_idstring

Canonical market object identifier

venuestring

Related platform code

resolved_fromstring

Input used to resolve the object

resolution_confidencestring

Object resolution confidence

dataobject | array

Present on assets / signals-style envelopes

Errors & fallback

200
assets_resolve name multi-match; confirm from data[] candidates.
200
The object resolved but no data is available; empty_reason may be not_covered_by_source, unsupported_metric, or limited_depth.
400
Invalid parameters or an ambiguous market listing; ambiguity responses include required_params + candidates.
401
The API key is missing or invalid.
403
The current key scope or plan cannot access this data domain.
404
The requested resource does not exist; source coverage gaps are not 404 responses.
402
Credits or monthly quota exhausted.
429
Request rate exceeded; retry_after is returned in the body and Retry-After in the response headers.