These endpoints are how you see the market on the zerohash Central Limit Order Book (CLOB) over REST — what's tradeable, how it's been trading, and what the book looks like right now. Together they cover the read side of a CLOB integration: discover the instruments, pull their recent statistics, and stream live order-book data.
For engineers and PMs, this is the REST alternative to consuming market data over FIX. FIX is the path for latency-sensitive systems that need full order-book synchronization over a persistent session; the REST endpoints are the simpler option when you want instrument reference data, headline stats, and a live feed without standing up FIX. Same book, lighter integration surface.
List instruments
Returns the CLOB instruments currently available to trade. This is your reference-data call — the source of truth for which symbols exist, so you don't hard-code a list that can drift as markets are added or removed. Call it to populate the instruments a user can pick from, and refresh it rather than assuming it's static.
Trade stats
Returns recent trading statistics for an instrument — the kind of headline market summary you'd show alongside a symbol (recent price and activity over a window). Use it to give users context on how something has been trading without having to reconstruct it yourself from raw trades.
Market data subscription
This is the live feed. Rather than a one-shot request, the market data subscription is a long-lived REST connection: you open it once, naming the instrument(s) you care about, and zerohash streams the state of the order book to you over that single connection for as long as it stays open. You get an initial snapshot of the book followed by a continuous flow of updates as orders are placed, changed, and removed — so your view stays current without polling.
When you subscribe you specify the symbols you want and can tune the feed — for example the book depth, whether you want a snapshot only rather than an ongoing stream, and whether prices should be aggregated by level or delivered per individual order.d
It's a stream, not a pollTreat this connection like a subscription: open it, consume the snapshot, then apply the incremental updates as they arrive to keep your local book in sync. Don't re-request on a timer — the whole point is that the connection stays open and pushes changes to you.