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
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, andXKRX. - Sessions include
is_tradableso clients can distinguish active trading from halts or auction/pre-open phases.
Recommended action
- Use
/rwa/market-hoursto 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
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_usdwherever HIP-3 liquidation metrics are returned, alongsideliquidation_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/symbolnow returns daily buckets forrange=allinstead of a singledate: "all"aggregate point.- Symbol timeseries requests fall back to live HIP-3 analytics data when a
dex_name+symbolpair 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_usdfor liquidation notional displays andliquidation_countfor fill counts. - If your client special-cased
range=allsymbol timeseries as a single aggregate row, update it to handle normal dated buckets.
June 28, 2026
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
exchangeandsymbol. - The options overview page uses this endpoint for stacked OI and volume trend charts.
Recommended action
- Use
/options/overview-history?range=90dwhen building cross-venue options trend views. Treatnotional_volume_24h_usdas a rolling 24h value at each hour, not hourly volume.
June 27, 2026
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-historyacceptexchange=deriveforsymbol=BTC,symbol=ETH, andsymbol=HYPE.- The same options endpoints accept
symbol=HYPEwithexchange=deribitorexchange=derive. - Unsupported exchange/symbol pairs return
400instead of falling back to another venue.
Recommended action
- Use
exchange=derivefor Derive BTC/ETH/HYPE data. Usesymbol=HYPE&exchange=deribitorsymbol=HYPE&exchange=derivefor HYPE options.
June 25, 2026
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-historyrequireexchange=deribit|binance|bybit|okx|derive./options/snapshotreads live snapshots from the matchingoptions_snapshot:{exchange}:{symbol}data source./options/atm-history,/options/metrics, and/options/surface-historyquery the matching exchange in options history data./options/atm-historyresponses now include the selectedexchange.
Recommended action
- Update options clients to pass
exchangeexplicitly. Useexchange=deribitto keep requesting Deribit data.
June 22, 2026
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
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
rangefor rolling lookbacks. - Use
startandendfor absolute custom windows. - This migration does not rename
interval,window_days, or liquidation-eventsince.
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/dexnow acceptrange./hip3-analytics/candlesnow accepts ISOstartandendin addition to legacy millisecond params./hip4-analytics/dashboardand/hip4-analytics/outcome/{outcome_id}now acceptrange./hip4-analytics/oi-eodnow acceptsstart./builder-analytics/dashboardnow acceptsrange./liquidations/aggregatesnow acceptsrange; allowed values remain1h,4h,12h, and24h./options/atm-historyand/options/surface-historynow acceptNdranges from1dthrough90d.
Compatibility
- Legacy
period,days,start_time,end_time, andmin_dayparams remain accepted until July 21, 2026. - Legacy requests include
Deprecation,Sunset,Link, andWarningheaders. - HIP-3, HIP-4, builder analytics, and liquidation aggregate responses keep
periodwhile also returningrange. - Options ATM history and surface history responses keep
dayswhile also returningrange.
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
Canonical symbol timeseries paths added
Canonical symbol timeseries paths were added for Open Interest and Volume.
Added
GET /oi/{symbol}/timeseriesGET /volume/{symbol}/timeseries
Compatibility
- Legacy
GET /oi/coin?coin={symbol}andGET /volume/coin?coin={symbol}remain accepted until July 21, 2026. - Legacy path responses include
DeprecationandSunsetheaders plus aLinkheader with the canonical successor path.
Response updates
- OI and Volume symbol timeseries responses return
timestampvalues as UTC ISO strings ending inZ. - OI symbol timeseries, Volume symbol timeseries, OI exchange totals, Volume exchange totals, and Volume/OI Ratio responses now include
unit,resolution, andnoticesmetadata. - Funding historical and settlement series points now return both the legacy
tfield and the canonicaltimestampfield.
Recommended action
- Use the canonical symbol timeseries paths and
start/endparams for new integrations.
June 21, 2026
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.