These endpoints are how you trade on the zerohash Central Limit Order Book (CLOB) over REST. They cover the full order-management loop — submit an order, cancel it, and query its state — giving you programmatic control over orders resting on the book without needing a FIX session.
For engineers and PMs, this is the REST alternative to FIX order entry. FIX remains the path for latency-sensitive, institutional-grade integrations that want a persistent session and full state synchronization; the REST API is the simpler, request/response option when you want to place and manage orders without standing up FIX infrastructure. Same order book, same matching engine — just a lighter integration surface.
What you can do
Order management here is the standard set of operations, each a single REST call:
- Submit an order — place a new order on the book. You choose the instrument, side, and size (by quantity or notional), the order type (market, limit, and so on), and a time-in-force that controls how long it rests — GTC (good-till-canceled), GTT (good-till-time), IOC (immediate-or-cancel), or FOK (fill-or-kill).
- Cancel an order — revoke a previously submitted order before it's fully filled.
- Query orders — search your orders to check status, fills, and average price, or pull the set of orders currently resting on the book.
Good to know
- Numbers come back as strings. The REST API returns all floats and integers as strings (e.g. "avg_px": "0") to preserve precision — parse accordingly rather than reading them as native numbers.
- Order state is what you act on. After submitting, use the query endpoints (or your own tracking) to confirm whether an order is working, filled, or canceled before taking the next action.