Liquidity API Endpoints Documentation#
This document provides an overview of all Liquidity-tagged API endpoints available in the Hyblock Professional API v2.Table of Contents#
Liquidation Events#
Liquidation#
Endpoint: GET /v2/liquidationDescription: Event where a trader's leveraged position is forced to close, due to margin not being enough to cover the loss.
Liquidation Levels#
Liquidation Levels Count#
Endpoint: GET /v2/liqLevelsCountDescription: Tracks the number of predicted liquidation levels in two modes:Anchored: Aggregated at fixed time intervals (daily, 4-hourly, or hourly, UTC).
Non-Anchored: Based on the most recent snapshot without anchoring.
For each mode, it reports:Total counts of long and short liquidation levels
Delta: Difference between long and short counts
This indicator helps pinpoint areas of liquidation pressure and reveals whether positioning skews toward longs or shorts. Users can choose between anchored or non-anchored views to fit their analysis.Summary: Liquidation Levels CountLiquidation Levels Size#
Endpoint: GET /v2/liqLevelsSizeDescription: Measures the relative strength of predicted liquidation levels to compare zones of potential liquidation pressure. Available in two modes:Anchored: Aggregated at fixed intervals (daily, 4-hourly, or hourly, UTC).
Non-Anchored: Based on the latest snapshot.
For each mode, it highlights:Relative long vs. short strength
Delta: Imbalance between long and short liquidation levels
This helps spot where liquidation clusters may be more influential and whether positioning skews to one side.Summary: Liquidation Levels SizeAnchored Liquidation Levels Count#
Endpoint: GET /v2/anchoredLiqLevelsCountDescription: Measures the number of predicted liquidation levels, anchored daily, 4-hourly, or hourly (UTC timezone). It captures the total count of long and short liquidation levels at each anchor point, along with the delta (difference between long and short counts). This provides insights into where liquidation pressure is concentrated and whether it skews toward longs or shorts.Summary: Anchored Liquidation Levels CountAnchored Liquidation Levels Size#
Endpoint: GET /v2/anchoredLiqLevelsSizeDescription: Measures the aggregated size of predicted liquidation levels, anchored daily, 4-hourly, or hourly (UTC timezone). It calculates the total notional size of long and short liquidation levels at each anchor point, along with the delta (difference between long and short sizes). This highlights not only the magnitude of potential liquidation events but also the directional imbalance between long and short positioning.Summary: Anchored Liquidation Levels SizeLiquidation Levels Trading View#
Endpoint: GET /v2/liquidationLevelsTVDescription: This endpoint provides access to open liquidation levels for specified coins and exchanges on TradingView charts, retrieving detailed information based on filters like leverage, position, tier, open duration, and open interest delta to volume ratio (oidv).Summary: Liquidation Levels Trading View
Leverage Metrics#
Average Leverage Used#
Endpoint: GET /v2/averageLeverageUsedDescription: This metric shows the average leverage used in long and short positions by top traders, identified as those within the top percentage holding the largest open position values.Summary: Top Trader Average Leverage UsedAverage Leverage Delta#
Endpoint: GET /v2/averageLeverageDeltaDescription: This metric captures the difference between the average leverage used in long and short positions by top traders, highlighting which side is utilizing more leverage.Summary: Top Trader Average Leverage DeltaTop Trader Margin Used#
Endpoint: GET /v2/topTraderMarginUsedDescription: Shows the total margin used by top traders, separated into margin used by long positions and short positions. This helps identify where leveraged positioning is concentrated among top participants.Summary: Top Trader Margin UsedTop Trader Margin Used Delta#
Endpoint: GET /v2/topTraderMarginUsedDeltaDescription: The net difference between margin used by top trader long positions and top trader short positions. Positive values indicate more long margin is used while negative values indicate more short margin is used.Summary: Top Trader Margin Used Delta
Liquidation Heatmap#
Endpoint: GET /v2/liquidationHeatmapDescription: The Liquidation Heatmap API endpoint, provided by Hyblock, predicts price buckets where liquidations may occur, enabling traders to visualize and anticipate potential liquidation levels. It delivers data on open predictive liquidations with the most recent timestamp, helping traders identify high-liquidity zones where significant liquidation events are likely.Summary: Liquidation HeatmapLiquidation Levels#
Endpoint: GET /v2/liquidationLevelsDescription: Liquidation Levels are estimates of potential price levels where liquidation events may occur.Summary: Liquidation LevelsCumulative Liq Level#
Endpoint: GET /v2/cumulativeLiqLevelDescription: Shows the general statistics of predicted liquidation levels, including the number of open long and short liquidation levels by size and count and the differences between them.Summary: Cumulative Liq Level
Common Parameters#
Most endpoints accept the following common query parameters:exchange: Exchange identifier (e.g., binance_perp_stable)
coin: Cryptocurrency symbol (e.g., BTC, ETH)
timeframe: Time interval (1m, 5m, 15m, 1h, 4h, 1d)
limit: Number of data points to return (default: 50)
startTime: Start timestamp (Unix timestamp)
endTime: End timestamp (Unix timestamp)
sort: Sort order (asc or desc)
Note: Some endpoints may have additional parameters specific to their functionality, such as anchor periods for anchored endpoints, leverage filters, or position filters.Authentication#
All endpoints require authentication via:API Key: x-api-key header
Rate Limits#
Rate Limit: 600 requests per minute
Burst Limit: 10 concurrent requests
Base URL#
All endpoints are prefixed with /v2/ and should be accessed via the base API URL.
For detailed request/response schemas and examples, please refer to the OpenAPI specification at /v2/openapi.json or visit the interactive API documentation.Modified at 2025-12-30 13:14:15