Perps - Token Liquidation Map
curl --request GET \
--url https://public-api.birdeye.so/perps/v1/token/liquidation_map \
--header 'X-API-KEY: <api-key>'import requests
url = "https://public-api.birdeye.so/perps/v1/token/liquidation_map"
headers = {"X-API-KEY": "<api-key>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {'X-API-KEY': '<api-key>'}};
fetch('https://public-api.birdeye.so/perps/v1/token/liquidation_map', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));{
"success": true,
"data": [
{
"low_price": 59355.907139877854,
"high_price": 60425.81178288396,
"position_count": 255,
"long_liq_size": 928.74387,
"long_liq_value": 55407181.36036671,
"short_liq_size": 0,
"short_liq_value": 0,
"cum_long_liq_size": 6978.52862,
"cum_long_liq_value": 483658047.865786,
"cum_short_liq_size": 0,
"cum_short_liq_value": 0
}
]
}{
"success": false,
"message": "Bad request"
}{
"success": false,
"message": "Unauthorized"
}{
"success": false,
"message": "Access Denied"
}{
"success": false,
"message": "Too many requests"
}{
"success": false,
"message": "Internal Server Error"
}Perps Token
Perps Token Liquidation Map
GET
/
perps
/
v1
/
token
/
liquidation_map
Perps - Token Liquidation Map
curl --request GET \
--url https://public-api.birdeye.so/perps/v1/token/liquidation_map \
--header 'X-API-KEY: <api-key>'import requests
url = "https://public-api.birdeye.so/perps/v1/token/liquidation_map"
headers = {"X-API-KEY": "<api-key>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {'X-API-KEY': '<api-key>'}};
fetch('https://public-api.birdeye.so/perps/v1/token/liquidation_map', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));{
"success": true,
"data": [
{
"low_price": 59355.907139877854,
"high_price": 60425.81178288396,
"position_count": 255,
"long_liq_size": 928.74387,
"long_liq_value": 55407181.36036671,
"short_liq_size": 0,
"short_liq_value": 0,
"cum_long_liq_size": 6978.52862,
"cum_long_liq_value": 483658047.865786,
"cum_short_liq_size": 0,
"cum_short_liq_value": 0
}
]
}{
"success": false,
"message": "Bad request"
}{
"success": false,
"message": "Unauthorized"
}{
"success": false,
"message": "Access Denied"
}{
"success": false,
"message": "Too many requests"
}{
"success": false,
"message": "Internal Server Error"
}- Usage Note
- Accessibility
- Chain Supported
- Returns a price-bucketed liquidation map for one Hyperliquid perpetual market.
- The response is organized around liquidation concentration by price zone, not by wallet or trade.
- Use this endpoint to understand where long and short liquidation pressure may cluster.
- Pair with token overview and open positions for fuller market-structure interpretation.
- Lite
- Starter
- Premium
- Business
- Enterprise
Hyperliquid
Compute Unit ⚙️
Compute Unit ⚙️
- This endpoint consumes
20 CUper request.
Use Cases 💡
Use Cases 💡
- Visualize liquidation pressure above and below the current market price.
- Build liquidation heatmaps for trader dashboards and risk tooling.
- Identify crowded zones that may accelerate moves once price enters them.
- Add liquidation context to market commentary, alerts, or derivatives analytics.
How to Use 🛠️
How to Use 🛠️
- Query the target Hyperliquid perp token market.
- Read the returned map as liquidation concentration across price bands.
- Compare nearby clusters with current price and open-interest context from
Perps Token Overview.
Best Practices ✅
Best Practices ✅
- Use this endpoint as a risk-context layer, not as a standalone trading signal.
- Plot the map visually to make clustering easier to interpret than raw tables alone.
- Reconcile liquidation zones with current positioning concentration before making directional assumptions.
Authorizations
API key for authentication
Headers
Specify the perpetuals exchange. Currently supports hyperliquid.
Available options:
hyperliquid Query Parameters
The symbol of a coin/token (e.g: BTC, SOL, ETH).
Was this page helpful?

