API Directory
Use this page as the map. Each service page below follows the same structure:
- endpoint index first
- request format next
- response example directly under each endpoint
Service Directory
| Service | Base URL | Use it for | Full reference |
|---|---|---|---|
| Matching Engine REST | https://api.liquideuclid.com | trading, balances, withdrawals, depth, recent trades | Matching Engine REST API |
| OMS REST | https://oms.liquideuclid.com | open orders, order history, single-order lookup | OMS API |
| Market Data REST | https://market.liquideuclid.com | klines and market snapshots | Market Data API |
| Market Data WebSocket | wss://market.liquideuclid.com/ws | live depth, trade, kline, and top-of-book streams | Market Data API |
Authentication
Use Authentication Headers for authenticated engine and OMS routes.
What Lives Where
Matching Engine REST
Use the engine when you need to submit or cancel orders, read balances, fetch account state, or create withdrawals.
Main route groups:
- public market routes:
/health,/time,/assets,/pairs,/depth/:pair_id,/trades/:pair_id - account routes:
/account,/balances/:user_id,/balances/:user_id/:asset,/trades/user/:user_id - order routes:
/orders,/signed_orders,/orders/cancel,/orders/cancel_replace,/orders/cancel_all - withdrawal routes:
/withdrawals,/withdrawals/status,/withdrawals/permit,/withdrawals/relay
OMS REST
Use OMS when you need user-facing order views after execution.
Main routes:
/health/orders/open/:user_id/orders/history/:user_id/orders/:order_id
Market Data REST and WebSocket
Use market-data for charting and live market views.
Main routes:
- REST:
/health,/klines/:pair_id - WebSocket:
depth,depth_diff,trade,kline,bookTicker