Market makers
Integrate market data, quoting and account updates with clear risk and recovery controls.
Build around the order book
The quoting loop
Drag to pan, or use arrow keys when the diagram is focused. Use plus and minus to zoom, and zero to fit. On a touch screen, pinch to zoom.
Market makers place and manage limit orders, respond to market conditions and control the inventory created by fills. Edel Markets supports automated clients through our product REST API and WebSockets. Commands enter the off-chain execution engine; Canton settlement follows separately.
A quoting strategy needs both a view of the market and a view of its account. Prices and depth inform the quote; working orders, fills, positions and available margin determine the exposure it can take. MCP is optional and is not required for market-making integration.
Keep each quote within the strategy's limits
Use current market rules for price and quantity precision, permitted sizes and risk limits. A post-only limit order expresses maker intent; reduce-only separately constrains position exposure. Set strategy limits for inventory, order size, outstanding orders and losses before enabling automated trading.
An accepted order can rest, partially fill or fill. Confirm what happened through account updates before recalculating the next quote. Cancelling an order removes only its unfilled remainder, and replacing it is not an atomic amendment: a fill can occur while cancellation is in progress.
Watch market health and account health separately
Establish the initial book and account snapshots, then use WebSockets for ongoing updates. A moving market feed does not prove that the account feed is current. Enable quoting only after the necessary subscriptions are accepted and state is reconciled.
| Input | What the strategy needs |
|---|---|
| Market state | Current prices, depth, funding and market status for the selected market. |
| Account state | Working orders, confirmed fills, positions and available risk capacity. |
| Connection health | Accepted subscriptions, valid private authentication and no unresolved gaps or stale state. |
Resolve uncertainty before adding exposure
Pause new exposure when private data becomes stale, a subscription is lost or an order's outcome is unknown. Preserve the original order and retry identities when a response is lost; a timeout is not proof of rejection. Reconcile working orders, fills and positions before resuming.
Reserve request capacity for cancellation and recovery. Disconnection does not establish that working orders have been cancelled, and a cancellation can race a fill. Keep the operator's stop procedure explicit. The market-maker operations reference covers stop conditions, request budgets, credential expiry and uncertain outcomes.
Prepare access and validate the integration
Edel Markets is on Devnet, with Testnet and Mainnet coming soon. Use the environment supplied for your integration and an owner-approved API key bound to the account and environment you intend to trade.
Start with read access, confirm account readiness and the enabled market catalogue, then test an explicitly authorized trading action with a defined size limit. Deposits, withdrawals and secure account setup remain owner actions in the app. Continue with market-maker integration, order commands and WebSocket integration for implementation details.