LiqSonar API
Pump events, the liquidation map, order-flow signals, order book walls and the cross-exchange verdict as JSON, plus an MCP server for AI assistants. Included in Pro; 60 requests per minute per key.
Your API key
Authentication
Send the key in the X-API-Key header (or Authorization: Bearer). The key works while your Pro is active.
curl -H "X-API-Key: lsk_..." "https://liqsonar.com/api/v1/pumps?days=7"
Endpoints
| Endpoint | Query parameters (default) | Returns |
|---|---|---|
GET /api/v1/pumps | days=1–90 (7), limit=1–200 (50) | Detected pumps and dumps with prices, timing, volume surge, open interest and liquidation volume, and the AI summary when available. Pass lang=en or lang=ru for the summary language (English by default). |
GET /api/v1/liquidation-levels/{symbol} | days=1|3|7 (1) | Estimated USD of long and short liquidations per price bin within ±12% of the price. |
GET /api/v1/signals | symbol, hours=1–168 (24), limit=1–1000 (200) | Order-flow signals on Binance futures: divergences, absorption, pressure, CVD flips, funding and volume spikes. Thresholds are still being calibrated. |
GET /api/v1/verdict/{symbol} | hours=1–24 (4) | Whether price moves with or against the order flow on Binance, Bybit, OKX and Bitget. |
GET /api/v1/walls | symbol, side=bid|ask, max_distance=0.1–5 (5), min_usd, limit=1–300 (100) | Large resting limit orders in the latest futures order book snapshot, largest first: exchange, side, price, USD size, distance from the mid price, how long the wall has stood and how many minutes of average volume would eat it. |
MCP server for AI assistants
Connect LiqSonar to Claude, ChatGPT, Cursor or any other MCP client and ask about the market in plain words: the assistant pulls signals, pumps, liquidation levels, walls and the verdict itself. Part of Pro, with the same limit of 60 requests per minute. Address (Streamable HTTP):
https://liqsonar.com/mcp
Claude.ai, Claude Desktop, ChatGPT — sign in, no key
Add a custom connector with the address above (Claude: Settings → Connectors → Add custom connector; ChatGPT: Settings → Apps & Connectors → Create, developer mode). The app opens LiqSonar: sign in and press Allow.
Claude Code, Cursor, Windsurf, VS Code — with a key or sign-in
These clients can sign in the same way (in Claude Code run /mcp after adding the server without a header) or use the API key:
Claude Code
claude mcp add --transport http liqsonar https://liqsonar.com/mcp --header "Authorization: Bearer lsk_..."
Cursor, Windsurf, VS Code
{
"mcpServers": {
"liqsonar": {
"url": "https://liqsonar.com/mcp",
"headers": { "Authorization": "Bearer lsk_..." }
}
}
}
Claude Desktop
{
"mcpServers": {
"liqsonar": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://liqsonar.com/mcp", "--header", "Authorization:Bearer lsk_..."]
}
}
}
For clients that support neither sign-in nor headers, put the key in the address. Keep such a URL private, like the key itself:
https://liqsonar.com/mcp?key=lsk_...
| Tool | Returns |
|---|---|
get_signals | Order-flow signals on Binance futures: divergences, absorption, pressure, CVD flips, funding and volume spikes. Thresholds are still being calibrated. |
get_pumps | Detected pumps and dumps with prices, timing, volume surge, open interest and liquidation volume, and the AI summary when available (language en or ru). |
get_liquidation_levels | Estimated USD of long and short liquidations per price bin within ±12% of the price. |
get_order_book_walls | Large resting limit orders in the latest futures order book snapshot, largest first: exchange, side, price, USD size, distance from the mid price, how long the wall has stood and how many minutes of average volume would eat it. |
get_verdict | Whether price moves with or against the order flow on Binance, Bybit, OKX and Bitget. |
get_my_alerts | Your active alerts with the current price of each pair and when each one last fired. |
get_my_watchlist | Coins on your watchlist with the current price and 24h change. |
get_my_wall_watches | Walls you track: price level, size when you started and now, alert threshold. |
Errors
401 — missing, unknown or revoked key; 402 — Pro has ended; 429 — more than 60 requests per minute. All errors return JSON with an error field.