TradePortfolio
DocsAPI changelog

API Changelog

Material API changes are listed here in reverse chronological order. Use this page to track endpoint updates, migration windows, and recommended client changes.


July 9, 2026

AddedRWAPro

RWA market hours endpoint added

The RWA API now includes Pro-tier UTC market-hours data for TradFi and RWA-linked venues.

What changed

  • Added GET /rwa/market-hours.
  • The endpoint returns UTC session intervals, current tradable status, next tradable session, upcoming holidays, and exchange metadata.
  • Exchange filters accept ids, short names, or MICs such as krx, KRX, and XKRX.
  • Sessions include is_tradable so clients can distinguish active trading from halts or auction/pre-open phases.

Recommended action

  • Use /rwa/market-hours to align RWA and TradFi-linked workflows with venue schedules. For live execution gates, use product-level calendars for venues with product-specific hours such as CME and SHFE.

June 29, 2026

ChangedHIP-3

HIP-3 liquidation metrics and symbol timeseries updated

HIP-3 analytics responses now expose liquidation USD value alongside fill count, and symbol timeseries requests can resolve non-precomputed symbols on demand.

What changed

  • Added liquidation_value_usd wherever HIP-3 liquidation metrics are returned, alongside liquidation_count.
  • HIP-3 liquidation count and value now count only the liquidated user fill, preventing counterparty fills from doubling the metric.
  • GET /hip3-analytics/timeseries/symbol now returns daily buckets for range=all instead of a single date: "all" aggregate point.
  • Symbol timeseries requests fall back to live HIP-3 analytics data when a dex_name + symbol pair is not present in the precomputed Redis snapshot.

Affected endpoints

  • /hip3-analytics/dashboard
  • /hip3-analytics/dex-detail
  • /hip3-analytics/by-dex
  • /hip3-analytics/by-symbol
  • /hip3-analytics/timeseries/symbol
  • /hip3-analytics/timeseries/dex-breakdown

Recommended action

  • Use liquidation_value_usd for liquidation notional displays and liquidation_count for fill counts.
  • If your client special-cased range=all symbol timeseries as a single aggregate row, update it to handle normal dated buckets.

June 28, 2026

AddedOptions

Options overview history added

The options API now includes an aggregate overview history endpoint for time-series dashboard widgets.

What changed

  • Added GET /options/overview-history.
  • The endpoint returns hourly USD-notional open interest and rolling 24h volume by exchange and symbol.
  • The options overview page uses this endpoint for stacked OI and volume trend charts.

Recommended action

  • Use /options/overview-history?range=90d when building cross-venue options trend views. Treat notional_volume_24h_usd as a rolling 24h value at each hour, not hourly volume.

June 27, 2026

AddedOptions

Options venues and symbols expanded

Options endpoints now support Derive for BTC, ETH, and HYPE options, with HYPE available on Deribit and Derive.

What changed

  • /options/snapshot, /options/atm-history, /options/metrics, and /options/surface-history accept exchange=derive for symbol=BTC, symbol=ETH, and symbol=HYPE.
  • The same options endpoints accept symbol=HYPE with exchange=deribit or exchange=derive.
  • Unsupported exchange/symbol pairs return 400 instead of falling back to another venue.

Recommended action

  • Use exchange=derive for Derive BTC/ETH/HYPE data. Use symbol=HYPE&exchange=deribit or symbol=HYPE&exchange=derive for HYPE options.

June 25, 2026

ChangedOptions

Options exchange parameter expanded

Options endpoints now require selecting a venue with `exchange`.

What changed

  • /options/snapshot, /options/atm-history, /options/metrics, and /options/surface-history require exchange=deribit|binance|bybit|okx|derive.
  • /options/snapshot reads live snapshots from the matching options_snapshot:{exchange}:{symbol} data source.
  • /options/atm-history, /options/metrics, and /options/surface-history query the matching exchange in options history data.
  • /options/atm-history responses now include the selected exchange.

Recommended action

  • Update options clients to pass exchange explicitly. Use exchange=deribit to keep requesting Deribit data.

June 22, 2026

DocsNotice

API change visibility improved

The API reference now gives users a persistent notice and changelog for material API changes.

What changed

  • Added an active reference notice to the API docs.
  • Added a dedicated API changelog for material endpoint updates, compatibility windows, and recommended client changes.
  • Added a changelog link from the API reference overview and API docs sidebar.

Recommended action

  • Review this changelog when upgrading clients or when an endpoint you use returns deprecation headers.

June 21, 2026

ChangedDeprecatedCompatibility window

Time query parameters standardized

Canonical time selector params were added to HIP-3, HIP-4, builder analytics, liquidation aggregates, and options history endpoints.

What changed

  • Use range for rolling lookbacks.
  • Use start and end for absolute custom windows.
  • This migration does not rename interval, window_days, or liquidation-event since.

Affected endpoints

  • /hip3-analytics/dashboard, /hip3-analytics/dex-detail, /hip3-analytics/by-dex, /hip3-analytics/by-symbol, /hip3-analytics/timeseries/symbol, /hip3-analytics/timeseries/dex-breakdown, /hip3-analytics/leaderboard, /hip3-analytics/oi-trends/total, and /hip3-analytics/oi-trends/dex now accept range.
  • /hip3-analytics/candles now accepts ISO start and end in addition to legacy millisecond params.
  • /hip4-analytics/dashboard and /hip4-analytics/outcome/{outcome_id} now accept range.
  • /hip4-analytics/oi-eod now accepts start.
  • /builder-analytics/dashboard now accepts range.
  • /liquidations/aggregates now accepts range; allowed values remain 1h, 4h, 12h, and 24h.
  • /options/atm-history and /options/surface-history now accept Nd ranges from 1d through 90d.

Compatibility

  • Legacy period, days, start_time, end_time, and min_day params remain accepted until July 21, 2026.
  • Legacy requests include Deprecation, Sunset, Link, and Warning headers.
  • HIP-3, HIP-4, builder analytics, and liquidation aggregate responses keep period while also returning range.
  • Options ATM history and surface history responses keep days while also returning range.

Recommended action

  • Update clients to send canonical params now. Existing legacy calls continue to work during the compatibility window, but should not be used for new integrations.

June 21, 2026

AddedDeprecated

Canonical symbol timeseries paths added

Canonical symbol timeseries paths were added for Open Interest and Volume.

Added

  • GET /oi/{symbol}/timeseries
  • GET /volume/{symbol}/timeseries

Compatibility

  • Legacy GET /oi/coin?coin={symbol} and GET /volume/coin?coin={symbol} remain accepted until July 21, 2026.
  • Legacy path responses include Deprecation and Sunset headers plus a Link header with the canonical successor path.

Response updates

  • OI and Volume symbol timeseries responses return timestamp values as UTC ISO strings ending in Z.
  • OI symbol timeseries, Volume symbol timeseries, OI exchange totals, Volume exchange totals, and Volume/OI Ratio responses now include unit, resolution, and notices metadata.
  • Funding historical and settlement series points now return both the legacy t field and the canonical timestamp field.

Recommended action

  • Use the canonical symbol timeseries paths and start / end params for new integrations.

June 21, 2026

ChangedNotice

Funding historical depth notices clarified

Funding historical and settlement docs were updated to describe available historical depth more precisely.

What changed

  • Dev tier is documented as a rolling 30-day window ending now.
  • Funding historical and settlement docs describe Pro and higher-tier historical depth as starting from September 2025.
  • Funding no-data and unavailable notices now mention that historical funding data starts in September 2025.

Recommended action

  • No client change is required. Review funding historical and settlement docs if your integration depends on historical depth assumptions.