Contents

Risk radar events

Risk radar events (whale moves, big liquidations, cascades, funding extremes, OI spikes, hacks, depegs, TVL drops, CEX outflows), newest first.

GET/api/v1/radar/eventsEvery keyPaginated

Description

Licence review: single liquidation orders reported by Binance / Bybit (big_liquidation, the record "largest single liquidation") are not published (also not in the stream and webhooks; a page can then hold fewer than limit items, so keep paging with meta.nextCursor); their funding / open-interest events keep venue and direction without the exchange’s figures; cascades and market-wide extremes leave out per-exchange amounts and keep their totals only where the total does not give one exchange’s amount.

Who can call it

Available with every key and keyless (X-Blockmetric-Access: public). Keys of Free accounts get free-tier data (real-time feeds, 30 days of history, heatmap over time for every coin over the last 24 hours, liquidation levels now for every coin, the same as the free web plan); Pro and Desk keys the data of their plan; API Dev / API Pro raise the limits.

No key
24 h
Free
30 days
Pro
365 days
Desk
1095 days
API Dev
365 days
API Pro
1095 days

History window per plan. Limits: Authentication & limits.

Parameters

Parameters of /radar/events
ParameterDescription
kindsstringComma-separated: whale_open, whale_close, whale_liquidated, big_liquidation, liq_cascade, funding_extreme, funding_flip, oi_spike, hack, depeg, tvl_drop, cex_outflow, hl_market_change, hl_manipulation, hl_adl, oracle_deviation, vault_drawdown, liq_extreme, protocol_outflow, incident, big_transfer, stablecoin_mint, stablecoin_burn, dex_whale_trade, risk_wallet_move, risk_wallet_listed (optional).
minSeverityinteger1 info, 2 notable, 3 major, 4 critical; default 1.1–4 · default 1
coinstringCoin name as on Hyperliquid (BTC, ETH, kPEPE, HIP-3 names like xyz:TSLA); case-insensitive.
sincestringISO 8601 time; only events after it (optional, a polling cursor). Clamped to the plan history (free key 30 days, keyless 24 h; meta.warnings says so).ISO 8601, e.g. 2026-10-23T12:00:00Z
limitintegerNumber of items, default 50, clamped to 1–500.1–500 · default 50
cursorstringNext page: the value of meta.nextCursor from the previous response (keep the other parameters unchanged). Cursors are signed: an edited cursor answers 400; paging stops at the plan history.
fieldsstringComma-separated fields of every item to return, e.g. id,ts,kind,severity,coin,title (case-insensitive). All other fields are left out, so large lists get much smaller; an unknown name answers 400 with the list of fields. Default: every field.
formatstringjson (default: the { data, meta } envelope) | csv (the rows with a header line; nested values as JSON text) | ndjson (one JSON object per row and line). csv and ndjson carry the meta block in headers: Link rel="next" and X-Blockmetric-Next-Cursor (next page), X-Blockmetric-Next-After (forward polling), X-Blockmetric-Updated-At, X-Blockmetric-Warnings, X-Blockmetric-License. Errors stay JSON.one of json, csv, ndjson · default json

Response fields

Every success is { data, meta }; these are the fields of data. meta is the same on every endpoint.

Response fields of /radar/events
FieldDescription
[].idintegerStable id of the item; on paginated feeds the order key together with ts.
[].tsstring (ISO 8601)Time of the event (ISO 8601 UTC).
[].kindstring (enum)Risk radar event kind.
[].severity"1" | "2" | "3" | "4"1 info, 2 notable, 3 major, 4 critical.
[].coinstring · nullableCoin name as on Hyperliquid (BTC, kPEPE, HIP-3 names like xyz:TSLA).
[].titlestringOne-line factual title in our own words.
[].bodystring · nullableDetails in our own words, or null.
[].dataanyKind-specific details (JSON) or null.
[].sourcestring · nullableData source (radar, defillama, …).

Errors

Methodology

Code snippets in these docs are licensed under MIT-0: copy them into your own code without attribution. The SDKs, CLI and MCP server will be, once published, Apache-2.0; the name Blockmetric is not licensed (forks must be renamed). Data from the API is governed by the API terms; third-party exchange data by the exchange’s terms.

LiveHyperliquid markets 9sOperationalHyperliquid positions & whales 0sOperationalLiquidation heatmap & levels 2sOperationalLighter markets & liquidations 9sOperationalLighter positions & heatmap 3sOperationalLighter RH positions & heatmap 1sOperationalBinance markets 29sOperationalBybit markets 2sOperationalBinance liquidations 9sOperationalBybit liquidations 9sOperationaldYdX positions & heatmap 0sOperationalGMX positions & heatmap 5sOperationalLong/short & open interest history 53sOperationalOrder books & trade flow 3sOperationalOn-chain transfers 5sOperationalSecurity monitor 36sOperationalBlockmetric Sentiment 12mOperationalOfficial news 1mOperationalAlert delivery 0sOperational10:09:27 UTCData: Blockmetric Research · Binance · Bybit