Walls, bot flow and sweeps from 18 exchange feeds — as an API

The events our terminal detects — liquidity walls, algorithmic flow, spikes and pushing — delivered as JSON for your dashboards, bots and research. Access is paid and set up for your use case.

Request API access See a sample event

Products

Liquidity Walls API

Standing limit-order walls across our spot and futures order-book streams.

Walls currently standing in the book, per coin and side.

Lifecycle: when a wall appeared and when it was gone.

Bucket-based prices and size tiers — context without order-book reconstruction.

Market Events API

Every detection type in one queryable event stream.

Walls, algo-flow, spikes and pushing patterns as unified events.

History with filters by coin, type, side and market.

Scored outcomes: price paths at fixed horizons after each event.

Algo Flow API — coming next.

Sample payload

One event, one JSON object

Payloads are bucket-based by design: prices and sizes arrive as tiers, not exact order-book levels.

{
  "id": 48201,
  "ts": 1754000000000,
  "coin": "SOL",
  "type": "wall",
  "side": "BID",
  "market": "spot",
  "source": "bybit",
  "price_bucket": "171-172",
  "size_usd_tier": "100k-250k",
  "status": "standing",
  "distance_to_spread_pct": 0.4,
  "age_seconds": 540,
  "detector_version": "2026-08-10"
}

How access works

From request to first query

1
Tell us what you need
Which signals and exchanges, how fresh, roughly how many requests. A few lines in the chat is enough — it opens with the questions already in it.
2
Get a quote
We reply with a plan and a price, usually within one business day.
3
Start querying
You get a key and the docs. One authenticated GET to /v1/events returns your events.

curl -H 'X-API-Key: hs_live_...' https://hookscreener.com/v1/events?type=wall

Pricing

Paid, priced by what you use

There is no public price list. A plan comes down to three things:

How fresh: delayed or real-time events.
How much: requests per month and how far back the history goes.
How it's used: your own research and bots, or shown to your users.

Tell us your case and we'll quote it.

Request API access

Embed / white-label our event feed

Run the detected-event stream inside your terminal, community or product — under your branding, with your limits.

Discuss white-label

Read this first

Limitations & legal

All data are derived, detected events computed by heuristic detectors over public exchange streams — not raw market data.
Classifications (walls, algo-flow, spikes, pushing) are heuristic labels; they are not statements about any market participant's identity or intent.
Data may be delayed, incomplete or revised; detectors and payload schemas evolve between versions.
Nothing in this API is investment advice or a recommendation to trade.
HookScreener is not affiliated with or endorsed by any exchange.
Payloads are bucket-based by design: prices and sizes are published as buckets and tiers, not exact order-book levels.

FAQ

Questions & answers

What data does the API return?

Detection events: liquidity walls with lifecycle, algo-flow runs, spikes and pushing patterns — each as a compact JSON object with coin, side, market, source, bucketed price/size and timestamps. It's the output of our detectors, not quotes or candles.

How fresh is the data?

Events are published as the detectors fire, and both real-time and delayed access are available. Scored outcomes need their horizons to pass, so events younger than 24 hours are still partially pending.

How is this different from price APIs?

Price APIs give you what everyone already has: OHLCV, tickers, order books. This API gives you interpreted microstructure — what our detectors found inside the books and tape across 18 spot and futures sources — already filtered, labeled and scored.

Is there a free tier?

No. Access is paid and set up per request: write to us from this page with what you're building, and we'll reply with a plan and a price.