The Trades service is your single source of truth for every trade zerohash has on record for your platform — regardless of how the trade was executed. Use it to retrieve and reconcile trades, and to submit off-venue trades for settlement.
How trades reach zerohash
A trade can land in the Trades service through several execution paths — and they all surface through the same retrieval endpoints:
- CLOB — trades matched and executed on zerohash's central limit order book.
- RFQ — trades executed against zerohash's request-for-quote liquidity.
- Platform-submitted (externally sourced liquidity) — trades your platform executed elsewhere and submits to be ledgered and settled at zerohash. You sourced the liquidity at a different venue; zerohash records the trade and acts as the calculation and settlement agent.
Whichever path a trade took, it is queryable through the same GET /trades and GET /trades/{trade_id} endpoints, with consistent fields — so reconciliation, reporting, and audit don't need to care where a trade originated.
Trade retrieval
Retrieval is the core of the Trades service. Use it to build statements, reconcile a period's activity, inspect a single trade, or find everything still awaiting settlement.
| Method & path | Purpose |
|---|---|
GET /trades | List the trades your platform can see — paginated and filterable |
GET /trades/{trade_id} | Retrieve the full detail for a single trade by its zerohash trade ID |
GET /tradesreturns trades from the last two months, paginated, with filtering by account, trade and settlement state, time window, counterparty, and execution reference.GET /trades/{trade_id}returns full detail for one trade — amounts, prices, settlement details, and counterparty information.
See Query Trades for the full parameter list and response schema.
Trade lifecycle
| State | Meaning |
|---|---|
accepted | Trade executed and recorded, awaiting settlement |
active | Settlement in progress |
terminated | Settlement complete (settled) |
You can receive trade status update notifications whenever a trade changes state instead of polling — the payload mirrors the GET /trades/{trade_id} response.
Post-trade settlement
The POST endpoints are for post-trade settlement. When your platform has matched and executed a trade — most commonly against liquidity you sourced at another venue — send the trade to zerohash to be ledgered and settled. Submit all the trade details (counterparties, amounts, prices, settlement schedule) and zerohash calculates each party's obligation and moves the assets to complete the trade.
| Method & path | Purpose |
|---|---|
POST /trades | Submit a single executed trade for settlement |
POST /trades/batch | Submit many executed trades at once |
Settlement model — obligations are expressed by the asset each party receives: the buy side receives the underlying, and the sell side receives the quoted_currency. This mirrors standard back-office trade reporting (FIX TradeCaptureReport) and is agnostic to symbol convention.
See Post Trade Settlement for the full request schema and examples.
Authentication
All Trades endpoints use standard zerohash API-key authentication — each request carries a signed Signature and `Time](https://docs.zerohash.com/reference/authentication)**.
Next steps
- Query Trades — retrieve and reconcile trades (
GET /trades, - Post Trade Settlement — submit trades for settlement (
POST /trades,POST /trades/batch)