You need an API key to place orders and view account state. An operator must provision your trader account. If you don’t have a key yet, ask your exchange operator.
Prerequisites
- An assigned API key (format:
exch_<32-hex-chars>, e.g.exch_1d4208be6fa84b8cb0a2e5cfa9508d5f) curlor any HTTP client- For WebSocket: a browser console,
websocat, or any WebSocket client
1
Check service health
Verify the exchange is live before trading.Expected response when healthy:
If
status is "degraded", the persistence backend is unhealthy (retrying, backpressured, or stopped). Trading continues in memory, but data may not be fully persisted.2
List available markets
Discover which markets are configured and their trading parameters.Example response:
3
Submit your first order
Place a limit buy order for 2 units of BTC-USD at price 100.Example response (order rested, no immediate fill):If the order crosses with a resting sell order,
fills will be non-empty and resting may be false (fully filled) or true (partially filled).4
View your open orders and fills
Check your current resting orders and executed trades.The
?market=BTC-USD query parameter is optional — omit it to see all markets.5
Connect to WebSocket and subscribe to market data
Subscribe to live L3 orderbook updates.
You receive one
snapshot message immediately after subscribing, followed by delta messages for every subsequent change. Always track the sequence number and resubscribe if you receive resync_required.6
Authenticate on WebSocket and receive order events
Authenticate your WebSocket session to enable trading and receive user-scoped events.
What’s next
REST API reference
Full documentation for every REST endpoint, request/response schema, and auth requirements.
WebSocket API
Complete message reference for all client and server WebSocket message types.
Error codes
HTTP status codes and WebSocket reject/error code reference.
Examples
More concrete curl, JavaScript, and Python examples.